Error when starting node

Hi Everyone,

for reference, i’m a windows user and this is basically my first foray into Ubuntu and the CLI in general. I’ve followed the guide for setting up a secret node on my NUC. When attempting to deploy the node with “bash start.sh” i get the following output:

user@node:~$ bash start.sh
CD into Discovery-Docker-Network
Making sure discovery-docker-network is up to date.
WARNING: The DOCKER_TAG variable is not set. Defaulting to a blank string.
WARNING: The SGX_MODE variable is not set. Defaulting to a blank string.
WARNING: The COMPOSE_PROJECT_NAME variable is not set. Defaulting to a blank string.
ERROR: Couldn’t connect to Docker daemon at http+docker://localhost - is it running?

If it’s at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
Start 9 workers on your Secret Node. Note : 9 is the max amount of workers you can run.
Creating .env file from template
Running in Hardware Mode, as per SGX_MODE=HW in .env file.
NODES is set to 9
Error: SGX driver not found. Run in simulation mode instead with:
./launch.bash -s

can anyone assist me to get up and running?
Thanks in advance!

2 Likes

Hi @R0bb0,

Did you follow this guide exactly?

https://secretnodes.org/#/tutorials/deploy-secretnode-nuc

@moonstash suggested to check and make sure you enabled SGX in the bios, based on the error you’re getting. Can you check that and let us know?

Thanks!

Hi @laura,

Thanks for your response. SGX is definitely enabled in the bios.

I followed the guide with the only deviation being that i used a different method to create the non root user with sudo privileges. for whatever reason i couldn’t get the code in the guide to work so i used:
$ sudo adduser

$ sudo usermod -aG sudo

I didn’t think it would make a difference? other than that i followed it to the letter.
Cheers!

1 Like

Okay, thanks for verifying that @R0bb0!

Can you give more details on the issue you ran into that made you deviate from the guide, including the steps and errors you saw?

I too have the exact same error/warning messages after setting up my node this evening and following the instructions on: https://secretnodes.org/#/tutorials/deploy-secretnode-nuc

I’m running Ubuntu 18.04.1 LTS // Dell Latitude // Core i5 7tg Gen

SGX is currently enabled in the bios.

Thanks.

1 Like

Thanks for confirming that you’re seeing the same error, @Stefan.Baranowski.

We’re looking into this! I’ll add your OS/hardware info to the issue.

Probably an error in the way i’m using the command…

useradd: Permission denied.

useradd: cannot lock /etc/passwd; try again later.

so rather than mess around with it i found a guide that helped me set up the sudo user

i’m using a NUC8i3BEH with ubuntu 18.04.3 LTS

That’s Ubuntu Server, correct?

From the guide:

Download Ubuntu Server 18.04 LTS ISO

Just to make sure recent updates didn’t break the guide, I thought I’d run through the NUC guide myself again with a fresh install of ubuntu.

I’m using the NUC8i7BEK which is actually the same as yours but shorter and with an i7 instead of an i3 in your NUC8i3BEH. The extra space in yours allows for an internal 2.5 hdd and that’s the only difference.

Everything worked when i ran through the guide, and while I did see some of these errors you described related to variables not set, they didn’t actually prevent the SGX enclave from being engaged later if you merely ignore the errors. For now I’m going to say you should ignore it as well, this guide so far is mostly a proof of concept that launches a non networked testnet environment. If you can get to the point where its saying the enclave was engaged then you should be fine. Keep in mind this guide should remain as simple as it is today but parts of it will change and improve right around when the networked version comes out.

1 Like

@R0bb0,

Also, when you get a chance can you post the error you got when you did the ssh into your node as root, before trying to add the nsn user? I just want to note it in case someone else has the same issue creating the non-root user.

Thanks!

1 Like

yes, ubuntu server, from the guide.

1 Like

well, its just giving me the options moreso than an error.

user@node:~$ useradd -m -s /bin/bash -G adm,systemd-journal,sudo $nsn && passwd $nsn
Usage: useradd [options] LOGIN
useradd -D
useradd -D [options]

Options:
-b, --base-dir BASE_DIR base directory for the home directory of the
new account
-c, --comment COMMENT GECOS field of the new account
-d, --home-dir HOME_DIR home directory of the new account
-D, --defaults print or change default useradd configuration
-e, --expiredate EXPIRE_DATE expiration date of the new account
-f, --inactive INACTIVE password inactivity period of the new account
-g, --gid GROUP name or ID of the primary group of the new
account
-G, --groups GROUPS list of supplementary groups of the new
account
-h, --help display this help message and exit
-k, --skel SKEL_DIR use this alternative skeleton directory
-K, --key KEY=VALUE override /etc/login.defs defaults
-l, --no-log-init do not add the user to the lastlog and
faillog databases
-m, --create-home create the user’s home directory
-M, --no-create-home do not create the user’s home directory
-N, --no-user-group do not create a group with the same name as
the user
-o, --non-unique allow to create users with duplicate
(non-unique) UID
-p, --password PASSWORD encrypted password of the new account
-r, --system create a system account
-R, --root CHROOT_DIR directory to chroot into
-s, --shell SHELL login shell of the new account
-u, --uid UID user ID of the new account
-U, --user-group create a group with the same name as the user
-Z, --selinux-user SEUSER use a specific SEUSER for the SELinux user mapping
–extrausers Use the extra users database

Did you do the command from the guide to set the USERNAME environment variable to nsn?

USERNAME=nsn

The adduser command is correct except for the two $nsn references. Those should be $USERNAME. The shell interprets the $USERNAME and substitutes with the value (as above).

The reason you’re getting the usage info for the command is that the nsn variable hasn’t been set so the command is missing that required argument.

I hope that helps :slight_smile: .

right, got it. so now the command works and i’m getting user already exists (as i created the user through a different means).

but still no luck when running the “bash start.sh” which produces the following output:

CD into Discovery-Docker-Network
Making sure discovery-docker-network is up to date.

ERROR: Couldn’t connect to Docker daemon at http+docker://localhost - is it running?

If it’s at a non-standard location, specify the URL with the DOCKER_HOST environment variable.
Start 9 workers on your Secret Node. Note : 9 is the max amount of workers you can run.
Running in Hardware Mode, as per SGX_MODE=HW in .env file.
NODES is set to 9
Error: SGX driver not found. Run in simulation mode instead with:
./launch.bash -s

Can you check and see if the /dev/isgx device file is present?

ls -l /dev/isgx

I’ll have to look into this more, but it seems like there could be a couple of issues:

  1. discover network isn’t starting up
  2. the SGX driver isn’t installed

ls: cannot access ‘/dev/isgx’: No such file or directory

from the guide:
7. When prompted “Do you want to install in current directory? [yes/no]” respond with “no” then say you want to install it in the “isgx” directory.

should we have created this directory prior to running the commands?

No, the install-sgx.sh script takes care of “all relevant SGX files and drivers”. But that’s a character special device file, not a directory so you wouldn’t be able to create it with a mkdir anyway.

To be honest I haven’t tried to deploy a secret node on an NUC. I don’t have the setup. I wonder if you could re-run the sendnodes.sh script and redirect the output to a log, and post that here?

bash sendnodes.sh > sendnodes.log 2&1 &
tail -f sendnodes.log

The first line runs the script and sends the output to sendnodes.log, including errors, and runs it in the background.
The 2nd line displays the sendnodes.log file as it’s being written to, until the script finishes so you can see it running and the messages.

Or you can just do this and wait for it to finish without viewing the output:

bash sendnodes.sh > sendnodes.log 2>&1

Also, can you verify that you’re running the script as your nsn user?

yes, running as nsn. see output below. links all broken as i couldnt post links…

nsn@znode:~$ bash sendnodes.sh
Downloading scripts to configure your Secret Node.
–2019-10-30 21:08:28-- ht tps://raw.githubusercontent. com/secretnodes/scripts/master/nuc-general/install-docker.sh
Resolving raw.githubusercontent. com (raw.githubusercontent. com)… 151.101.96.133
Connecting to raw.githubusercontent. com (raw.githubusercontent. com)|151.101.96.133|:443… connected.
HT TP request sent, awaiting response… 200 OK
Length: 1452 (1.4K) [text/plain]
Saving to: ‘install-docker.sh’

install-docker.sh 100%[====================================================>] 1.42K --.-KB/s in 0s

2019-10-30 21:08:29 (5.38 MB/s) - ‘install-docker.sh’ saved [1452/1452]

–2019-10-30 21:08:30-- ht tps://raw.githubusercontent. com/secretnodes/scripts/master/nuc-general/install-sgx.sh
Resolving raw.githubusercontent. com (raw.githubusercontent. com)… 151.101.96.133
Connecting to raw.githubusercontent. com (raw.githubusercontent. com)|151.101.96.133|:443… connected.
HT TP request sent, awaiting response… 200 OK
Length: 1645 (1.6K) [text/plain]
Saving to: ‘install-sgx.sh’

install-sgx.sh 100%[====================================================>] 1.61K --.-KB/s in 0s

2019-10-30 21:08:30 (8.33 MB/s) - ‘install-sgx.sh’ saved [1645/1645]

–2019-10-30 21:08:31-- ht tps://raw.githubusercontent. com/secretnodes/scripts/master/nuc-general/start.sh
Resolving raw.githubusercontent. com (raw.githubusercontent. com)… 151.101.96.133
Connecting to raw.githubusercontent. com (raw.githubusercontent. com)|151.101.96.133|:443… connected.
HT TP request sent, awaiting response… 200 OK
Length: 348 [text/plain]
Saving to: ‘start.sh’

start.sh 100%[====================================================>] 348 --.-KB/s in 0s

2019-10-30 21:08:32 (4.75 MB/s) - ‘start.sh’ saved [348/348]

–2019-10-30 21:08:33-- ht tps://raw.githubusercontent. com/secretnodes/scripts/master/nuc-general/install-enigma-node.sh
Resolving raw.githubusercontent. com (raw.githubusercontent. com)… 151.101.96.133
Connecting to raw.githubusercontent. com (raw.githubusercontent. com)|151.101.96.133|:443… connected.
HT TP request sent, awaiting response… 200 OK
Length: 308 [text/plain]
Saving to: ‘install-enigma-node.sh’

install-enigma-node.sh 100%[====================================================>] 308 --.-KB/s in 0s

2019-10-30 21:08:33 (4.11 MB/s) - ‘install-enigma-node.sh’ saved [308/308]

–2019-10-30 21:08:34-- ht tps://raw.githubusercontent. com/secretnodes/scripts/master/nuc-general/upgrade.sh
Resolving raw.githubusercontent. com (raw.githubusercontent. com)… 151.101.96.133
Connecting to raw.githubusercontent. com (raw.githubusercontent. com)|151.101.96.133|:443… connected.
HT TP request sent, awaiting response… 200 OK
Length: 285 [text/plain]
Saving to: ‘upgrade.sh’

upgrade.sh 100%[====================================================>] 285 --.-KB/s in 0s

2019-10-30 21:08:34 (3.71 MB/s) - ‘upgrade.sh’ saved [285/285]

–2019-10-30 21:08:35-- ht tps://raw.githubusercontent. com/secretnodes/scripts/master/nuc-general/install-fixes.sh
Resolving raw.githubusercontent. com (raw.githubusercontent. com)… 151.101.96.133
Connecting to raw.githubusercontent. com (raw.githubusercontent. com)|151.101.96.133|:443… connected.
HT TP request sent, awaiting response… 200 OK
Length: 426 [text/plain]
Saving to: ‘install-fixes.sh’

install-fixes.sh 100%[====================================================>] 426 --.-KB/s in 0s

2019-10-30 21:08:36 (6.48 MB/s) - ‘install-fixes.sh’ saved [426/426]

–2019-10-30 21:08:37-- ht tps://raw.githubusercontent. com/secretnodes/scripts/master/nuc-general/uninstall.sh
Resolving raw.githubusercontent. com (raw.githubusercontent. com)… 151.101.96.133
Connecting to raw.githubusercontent. com (raw.githubusercontent. com)|151.101.96.133|:443… connected.
HT TP request sent, awaiting response… 404 Not Found
2019-10-30 21:08:37 ERROR 404: Not Found.

Change permissions for install sgx, install docker, start, & upgrade scripts.
Running upgrade.sh script.
Update & Upgrade System.
Hit:1 ht tp://au.archive.ubuntu. com/ubuntu bionic InRelease
Hit:2 ht tp://au.archive.ubuntu. com/ubuntu bionic-updates InRelease
Hit:3 ht tp://au.archive.ubuntu. com/ubuntu bionic-backports InRelease
Hit:4 ht tp://au.archive.ubuntu. com/ubuntu bionic-security InRelease
Hit:5 ht tps://download.docker. com/linux/ubuntu bionic InRelease
Reading package lists… Done
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists… Done
Building dependency tree
Reading state information… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Complete!
The script is not finished yet. Next we will install docker, please wait.
Running install-docker.sh script.
===> Running step 1
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 617 0 617 0 0 1307 0 --:–:-- --:–:-- --:–:-- 1304
100 16.1M 100 16.1M 0 0 1824k 0 0:00:09 0:00:09 --:–:-- 2575k
===> Running step 2
===> Running Step 4
Hit:1 ht tp://au.archive.ubuntu. com/ubuntu bionic InRelease
Hit:2 ht tp://au.archive.ubuntu. com/ubuntu bionic-updates InRelease
Hit:3 ht tp://au.archive.ubuntu. com/ubuntu bionic-backports InRelease
Hit:4 ht tps://download.docker. com/linux/ubuntu bionic InRelease
Hit:5 ht tp://au.archive.ubuntu. com/ubuntu bionic-security InRelease
Reading package lists… Done
Building dependency tree
Reading state information… Done
All packages are up to date.
===> install prerequisite packages which let apt use packages over HT TPS
Reading package lists… Done
Building dependency tree
Reading state information… Done
ca-certificates is already the newest version (20180409).
curl is already the newest version (7.58.0-2ubuntu3.8).
software-properties-common is already the newest version (0.96.24.32.11).
apt-transport-ht tps is already the newest version (1.6.12).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
===> Add the GPG key for the official Docker repository to your system
OK
===> Add the Docker repository to APT sources
Hit:1 ht tp://au.archive.ubuntu. com/ubuntu bionic InRelease
Hit:2 ht tp://au.archive.ubuntu. com/ubuntu bionic-updates InRelease
Hit:3 ht tp://au.archive.ubuntu. com/ubuntu bionic-backports InRelease
Hit:4 ht tps://download.docker. com/linux/ubuntu bionic InRelease
Hit:5 ht tp://au.archive.ubuntu. com/ubuntu bionic-security InRelease
Reading package lists… Done
===> update the package database with the Docker packages from the newly added repo
Hit:1 ht tp://au.archive.ubuntu. com/ubuntu bionic InRelease
Hit:2 ht tp://au.archive.ubuntu. com/ubuntu bionic-updates InRelease
Hit:3 ht tp://au.archive.ubuntu. com/ubuntu bionic-backports InRelease
Hit:4 ht tp://au.archive.ubuntu. com/ubuntu bionic-security InRelease
Hit:5 ht tps://download.docker. com/linux/ubuntu bionic InRelease
Reading package lists… Done
Building dependency tree
Reading state information… Done
All packages are up to date.
Reading package lists… Done
Building dependency tree
Reading state information… Done
Calculating upgrade… Done
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
===> install from the Docker repo instead of the default Ubuntu repo
docker-ce:
Installed: 5:19.03.4~3-0~ubuntu-bionic
Candidate: 5:19.03.4~3-0~ubuntu-bionic
Version table:
*** 5:19.03.4~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
100 /var/lib/dpkg/status
5:19.03.3~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:19.03.2~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:19.03.1~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:19.03.0~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.9~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.8~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.7~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.6~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.5~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.4~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.3~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.2~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.1~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
5:18.09.0~3-0~ubuntu-bionic 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
18.06.3~ce~3-0~ubuntu 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
18.06.2~ce~3-0~ubuntu 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
18.06.1~ce~3-0~ubuntu 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
18.06.0~ce~3-0~ubuntu 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
18.03.1~ce~3-0~ubuntu 500
500 ht tps://download.docker. com/linux/ubuntu bionic/stable amd64 Packages
===> Install Docker
Reading package lists… Done
Building dependency tree
Reading state information… Done
docker-ce is already the newest version (5:19.03.4~3-0~ubuntu-bionic).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
===> Verify Docker Compose installation was successful.
===> type : docker-compose --version
===> Docker should now be installed, the daemon started, and the process enabled to start on boot. Check that it’s running
===> type : sudo systemctl status docker
<3 from ht tps://secretnodes. org
The script is not finished yet. Next we will install sgx, please wait.
Running install-sgx.sh script.
apt-get dpkg & update
Hit:1 ht tp://au.archive.ubuntu. com/ubuntu bionic InRelease
Hit:2 ht tp://au.archive.ubuntu. com/ubuntu bionic-updates InRelease
Hit:3 ht tp://au.archive.ubuntu. com/ubuntu bionic-backports InRelease
Hit:4 ht tps://download.docker. com/linux/ubuntu bionic InRelease
Hit:5 ht tp://au.archive.ubuntu. com/ubuntu bionic-security InRelease
Reading package lists… Done
Reading package lists… Done
Building dependency tree
Reading state information… Done
dpkg is already the newest version (1.19.0.5ubuntu2.3).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
To install the Intel® SGX PSW, first install the following tools
Reading package lists… Done
Building dependency tree
Reading state information… Done
libprotobuf-dev is already the newest version (3.0.0-9.1ubuntu1).
libcurl4-openssl-dev is already the newest version (7.58.0-2ubuntu3.8).
libssl-dev is already the newest version (1.1.1-1ubuntu2.1~18.04.4).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
To install the Intel® SGX SDK, install the following:
Reading package lists… Done
Building dependency tree
Reading state information… Done
build-essential is already the newest version (12.4ubuntu1).
python is already the newest version (2.7.15~rc1-1).
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Downloading the required SGX files.
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 26688 100 26688 0 0 143k 0 --:–:-- --:–:-- --:–:-- 143k
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 1667k 100 1667k 0 0 1962k 0 --:–:-- --:–:-- --:–:-- 1960k
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 28686 100 28686 0 0 142k 0 --:–:-- --:–:-- --:–:-- 142k
% Total % Received % Xferd Average Speed Time Time Time Current
Dload Upload Total Spent Left Speed
100 18.4M 0 18.4M 0 0 2657k 0 --:–:-- 0:00:07 --:–:-- 2739k
Setting permissions for driver & SDK.
Installing SGX driver.
Unpacking Intel SGX Driver … done.
Verifying the integrity of the install package … done.
Installing Intel SGX Driver …
/tmp/sgx-driver-LXzsMF ~
install -d /opt/intel/sgxdriver/package
install -d /opt/intel/sgxdriver/scripts
install package/* /opt/intel/sgxdriver/package
install scripts/* /opt/intel/sgxdriver/scripts
~
/opt/intel/sgxdriver/package ~
make -C /lib/modules/4.15.0-66-generic/build SUBDIRS=/opt/intel/sgxdriver/package modules
make[1]: Entering directory ‘/usr/src/linux-headers-4.15.0-66-generic’
CC [M] /opt/intel/sgxdriver/package/sgx_main.o
CC [M] /opt/intel/sgxdriver/package/sgx_page_cache.o
CC [M] /opt/intel/sgxdriver/package/sgx_ioctl.o
CC [M] /opt/intel/sgxdriver/package/sgx_vma.o
CC [M] /opt/intel/sgxdriver/package/sgx_util.o
CC [M] /opt/intel/sgxdriver/package/sgx_encl.o
CC [M] /opt/intel/sgxdriver/package/sgx_encl2.o
LD [M] /opt/intel/sgxdriver/package/isgx.o
Building modules, stage 2.
MODPOST 1 modules
CC /opt/intel/sgxdriver/package/isgx.mod.o
LD [M] /opt/intel/sgxdriver/package/isgx.ko
make[1]: Leaving directory ‘/usr/src/linux-headers-4.15.0-66-generic’
Installing psw
(Reading database … 73881 files and directories currently installed.)
Preparing to unpack …/libsgx-enclave-common_2.6.100.51363-bionic1_amd64.deb …
Unpacking libsgx-enclave-common (2.6.100.51363-bionic1) over (2.6.100.51363-bionic1) …
Setting up libsgx-enclave-common (2.6.100.51363-bionic1) …
Installing aesmd.service service … done.
Processing triggers for libc-bin (2.27-3ubuntu1) …
(Reading database … 73881 files and directories currently installed.)
Preparing to unpack …/libsgx-enclave-common-dev_2.6.100.51363-bionic1_amd64.deb …
Unpacking libsgx-enclave-common-dev (2.6.100.51363-bionic1) over (2.6.100.51363-bionic1) …
Setting up libsgx-enclave-common-dev (2.6.100.51363-bionic1) …
Processing triggers for libc-bin (2.27-3ubuntu1) …
Installing SGX on Linux. Chose to install SGX in current directory, respond with ‘no’.

Do you want to install in current directory? [yes/no] : no

Please input the directory which you want to install in : isgx
Unpacking Intel SGX SDK … done.
Verifying the integrity of the install package … done.
Installing Intel SGX SDK … done.
/tmp/sgx-sdk-hJYGFN ~
install -d /home/nsn/isgx/sgxsdk
cp -r package/* /home/nsn/isgx/sgxsdk
install -d /home/nsn/isgx/sgxsdk/scripts
install scripts/* /home/nsn/isgx/sgxsdk/scripts
chmod +x /home/nsn/isgx/sgxsdk/bin/sgx-gdb
~
uninstall.sh script generated in /home/nsn/isgx/sgxsdk

Installation is successful! The SDK package can be found in /home/nsn/isgx/sgxsdk

Please set the environment variables with below command:

source /home/nsn/isgx/sgxsdk/environment
Setting LD LIBRARY PATH
<3 from ht tps://secretnodes. org
Running install-enigma-node.sh
Downloading and installing enigma node software.
Pre Genesis Games | DevNet | Discovery-Docker-Network.
fatal: destination path ‘discovery-docker-network’ already exists and is not an empty directory.
Running install-fixes.sh
Please report any issues you face at ht tps://t.me/secretnodes
Implimenting fix for docker caused networking issue ht tps://github. com/docker/libnetwork/issues/2187
Note: To upgrade all scripts, you must merely run sendnodes.sh again.
Applying fixes.
Please report any issues you face at ht tps://t.me/secretnodes
Implimenting fix for docker caused networking issue ht tps://github. com/docker/libnetwork/issues/2187
Note: To upgrade all scripts, you must merely run sendnodes.sh again.
<3 from ht tps://secretnodes. org