remarks on installation

[drazioti]

Δοκιμασα την εγκατάσταση σε

$lsb_release -a
LSB Version:	core-11.1.0ubuntu4-noarch:printing-11.1.0ubuntu4-noarch:security-11.1.0ubuntu4-noarch
Distributor ID:	Ubuntu
Description:	Ubuntu 22.04.5 LTS
Release:	22.04
Codename:	jammy

---

• Δεν καταλαβαινω γιατι θέλεις root, δηλ. εγκατάσταση στο /opt.
• Η εξάρτηση απο την java γενικα αρνητικο για την πλατοφορμα
• Πρέπει λίγο να εξηγησεις στο readmeγιατι θέλεις ssh (σε επιπεδο root!)

---

Quick Installation

-Εδω ο χρηστης secureu έχει "passwordless sudo". Αυτό ακόμη και για testing δεν φαινεται σωστό.
-Επίσης δημιουργεις systemd services (secureu-backend, secureu-frontend) και ενεργοποιουνται στο boot
Δηλ. το συστημα επηρεαζεται αρκετά. To πιο ασφαλές είναι να το τρέξω σε vm. Οπότε θα επανελθω όταν το κάνω.

Manual Installation

[1] apt install -y docker.io nodejs npm default-jdk golang-go (also need sudo)
so better write
$sudo apt install -y docker.io nodejs npm default-jdk golang-go

[2] Also note:

during installation you may encounter a dependency conflict if Docker’s upstream containerd.io package is already installed (instead of Ubuntu’s containerd, which docker.io depends on). In that case apt may fail with:

The following packages have unmet dependencies:
 containerd.io : Conflicts: containerd
E: Error, pkgProblemResolver::Resolve generated breaks, this may be caused by held packages.

[MikeAnast]

the secur-eu platform needs root access write in order to monitor the syslog files, folders, directories with the SEUXDR tool and to monitor the network traffic with the AD&DTM tool

[drazioti]

First attempt.

[1] Set up a vm
This time in a fresh install of ubuntu 24.04 in a virtualbox with
storage 100GB, 6 cores, 7GB ram.

lsb_release -a
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 24.04.4 LTS
Release:	24.04
Codename:	noble

We defined a second network adapter (from settings in virtualbox).

This time for the installation we used the script install.sh.

Why the title is "Networking notes for VirtualBox / multi-NIC hosts", since you provide a method for installation. It wouldn't better "Installation notes using a bash script"?

In order to avoid some trivial errors, first, we need to install java 17, so I started
sudo apt install openjdk-17-jdk
and then select java 17 from
sudo update-alternatives --config java

So I recommend to avoid step 4 of install.sh. In the script you installed Java 17 but you do not select it.
So you may change README & install.sh accordingly.

[2] Executing install.sh
I set
$server=192.168.xxx.xxx
the IP of the vm and then
$sudo SERVER_IP=$server install.sh

install.sh finished correctly (without errors).

[3] I preferred the "manual way"
cd /home/$USER/secureu-platform/backend && ./start.sh
in order to print possible errors.
This is the most time/storage consuming step (~5 hours) and added ~80GB! to the storage.
The 8/10 Step (ollama) and 9/10 are the most time consuming.

So I suggest at least 130GB storage for the vm

During the installation we got the following errors
=> ERROR [5/5] RUN pip install --no-cache-dir -r requirements.txt
and we ended with

--------------------

  10 |     

  11 |     # Upgrade pip and install dependencies

  12 | >>> RUN pip install --no-cache-dir -r requirements.txt

  13 |     

  14 |     EXPOSE 8000

--------------------

failed to solve: process "/bin/sh -c pip install --no-cache-dir -r requirements.txt" did not complete successfully: exit code: 1

So I changed in the dockerfile of darkweb the first line to
$FROM python:3.11-slim
and then
$docker compose build --no-cache
Reboot and then again
cd /home/$USER/secureu-platform/backend && ./start.sh
and after some time the system becomes non responsive.

This, I suppose we run out of memory so added one more GB to vm, now we have 8GB. Change the logic and I will try it again.
Again after some time the system becomes non responsive.

I think the problem can be described as below.

The logic behind start.sh is : pull-->build->initialize-->run for each component.
However, it seems more efficient to follow the scheme : pre-pull all the images (first step) ->initialize each component-->start.