Switching to Docker Enterprise

getting the following error when doing a docker pull:

docker pull storjlabs/storagenode:beta
beta: Pulling from storjlabs/storagenode
no matching manifest for windows/amd64 10.0.14393 in the manifest list entries

running windows server 2016.
any ideas?

Install the Linux VM with a docker and use it from there.
Also you can use an experimental Windows installer

1 Like

Running Ubuntu (non-server), LTS. Docker and mount point seem to be fine, but getting the following error:
docker: Error response from daemon: invalid mount config for type “bind”: bind source does not exist: /mnt/storj/Identity storjnode/.

Running the following to start the container:
sudo docker run -d --restart unless-stopped -p 28967:28967 -p 127.0.0.1:14002:14002 -e WALLET=“WalletAddy” -e EMAIL="MyGmail@gmail.com" -e ADDRESS=“Domain.com:28967” -e BANDWIDTH=“100TB” -e STORAGE=“7TB” --mount type=bind,source=/mnt/storj/Identity/storjnode/,destination=/app/identity --mount type=bind,source=/mnt/storj/Data/,destination=/app/config --name storagenode storjlabs/storagenode:beta

If I use -v instead of --mount, it starts somewhat. It throws the following error in the docker logs:
file or directory not found error: open identity/identity.cert: no such file or directory

I’ve confirmed that I can access the directory /mnt/storj, and it’s a Windows Share mount. Could that be the reason? The goal of this is to migrate from Windows Server 2016 to Ubuntu VM.

I think your folder should have a name storagenode, not the storjnode
But please, give me an output of the command:

ls -l /mnt/storj
ls -l /mnt/storj/Identity

sudo docker run -d --restart unless-stopped -p 28967:28967 -p 127.0.0.1:14002:14002 -e WALLET=“WalletAddy” -e [EMAIL="MyGmail@gmail.com](mailto:EMAIL=%22MyGmail@gmail.com)" -e ADDRESS=“[Domain.com:28967](http://domain.com:28967/)” -e BANDWIDTH=“100TB” -e STORAGE=“7TB” --mount type=bind,source=/mnt/storj/Identity/storagenode/,destination=/app/identity --mount type=bind,source=/mnt/storj/Data/,destination=/app/config --name storagenode storjlabs/storagenode:beta

Thanks for catching that. Changed the identity path, but getting a new error (Similar to -v error was getting before):
file or directory not found error: open Identity/identity.cert: no such file or directory

storj@storj-Virtual-Machine:/mnt/storj$ ls -l /mnt

total 4
drwxr-xr-x 2 root root 4096 Oct 4 20:25 storj
storj@storj-Virtual-Machine:/mnt/storj$ ls -l /mnt/storj/
ls: cannot read symbolic link ‘/mnt/storj/info.db’: No such file or directory
ls: cannot read symbolic link ‘/mnt/storj/info.db-shm’: No such file or directory
ls: cannot read symbolic link ‘/mnt/storj/info.db-wal’: No such file or directory
total 25
drwxr-xr-x 2 root root 0 Feb 11 2019 Data
-rwxr-xr-x 1 root root 7654 Jul 16 17:59 earnings.py
drwxr-xr-x 2 root root 0 Aug 5 11:30 Grafana
drwxr-xr-x 2 root root 0 Feb 6 2019 Identity
l--------- 1 root root 0 Aug 5 09:11 info.db
l--------- 1 root root 0 Aug 5 09:11 info.db-shm
l--------- 1 root root 0 Aug 5 09:11 info.db-wal
drwxr-xr-x 2 root root 0 Feb 6 2019 ‘$RECYCLE.BIN’
-rwxr-xr-x 1 root root 4852 Jul 19 08:59 StorjAudit.sh
-rwxr-xr-x 1 root root 54 Feb 6 2019 StorjDashboard.bat
-rwxr-xr-x 1 root root 45 Feb 6 2019 StorjDashboard.ps1
-rwxr-xr-x 1 root root 66 Oct 6 16:17 storj_dashboard.sh
-rwxr-xr-x 1 root root 50 Feb 20 2019 StorjStart.bat
-rwxr-xr-x 1 root root 341 Jun 8 13:48 StorjStart.ps1
-rwxr-xr-x 1 root root 49 Jun 4 20:43 StorjStop.bat
-rwxr-xr-x 1 root root 33 Jun 4 20:43 StorjStop.ps1
-rwxr-xr-x 1 root root 52 Feb 6 2019 StorjUpgrade.bat
-rwxr-xr-x 1 root root 519 Oct 6 16:07 StorjUpgrade.ps1
-rwxr-xr-x 1 root root 694 Oct 6 17:47 storj_upgrade.sh
drwxr-xr-x 2 root root 0 Feb 6 2019 ‘System Volume Information’

Symbolic links wont work. Such setup is not supported.
Please, show content of the Identity:

ls -l /mnt/storj/Identity/

Also, please, remove the config.yaml and restart the node

Removed symlinks.

storj@storj-Virtual-Machine:/mnt/storj$ ls -l /mnt/storj/Identity/
total 14
-rwxr-xr-x 1 root root  530 Feb  6  2019 ca.1549496854.cert
-rwxr-xr-x 1 root root 1064 Feb  6  2019 ca.cert
-rwxr-xr-x 1 root root  227 Feb  6  2019 ca.key
-rwxr-xr-x 1 root root 1072 Feb  6  2019 identity.1549496854.cert
-rwxr-xr-x 1 root root 1606 Feb  6  2019 identity.cert
-rwxr-xr-x 1 root root  227 Feb  6  2019 identity.key
drwxr-xr-x 2 root root    0 Feb  6  2019 storagenode

Restarted the node…now playing the waiting game. Is there any sort of API to see if communication is working between my node and a satellite?

Node ID: 1765RRSLTetCWq9omHzemihN3GzAgXhgbNNxDJ77t6tj6ejxLF

2 posts were merged into an existing topic: FATAL Unrecoverable error {“error”: “Error creating tables for master database on storagenode: migrate: storage node database error: migrate tables:: database is locked

Yes.

Also, you can see the GUI dashboard: https://documentation.storj.io/setup/cli/dashboard

I saw that thread and was hoping it wasn’t the case. So in theory, I’m running Docker in a Linux VM on Windows Server 2016 with Hyper-V. The disk I want to use is local to the Windows Server box, Letter S:. It’s technically not networked, but I’d imagine that the network path is required to access it in the VM, right?

So I’m probably already DQ’ed for having my node down for 2 days. What’s the recommended path forward for this? Would it be to get a new Node ID (but I forfeit my ‘stashed’ coins), or is there someway to recover? Is there a way to attach a disk to a VM with Hyper-V?

Your node is not disqualified for downtime. This check is under construction:

Yes. You can attach the disk to the VM on Hyper-V.
However, I would recommend to create a virtual disk and attach it to the VM.
Partition it and format it to the ext4. Add it to the /etc/fstab. Then move all data to there (from SMB attached drive).

Short term you can carefully use this suggestion:

I should mention, that on Windows 10 in the VM Ubuntu server 18.04 LTS on Hyper-V the SMB share is worked fine - my node is successfully migrated to the new version without any issues.
Seems SMB on Windows Server is working differently.