This is a first Storj install on my clean install Ubuntu 19.04 box and I believe have the Storj Node set up correctly with the ports forwarded to the proper internal IP address. However when I try to view the dashboard, I get the following error.
Error response from daemon: Container (id removed) is restarting, wait until the container is running
I’ve tried stopping, starting, removing, upgrading the container, but nothing seems to change this error message. Any ideas?
FYI - this is the second node I’ve set up, however it’s the first on a Linux box. The previous node was on a Windows 10 Pro machine that had to be rebuilt. I did not have these issues when setting up the node on the Windows machine.
your error looks like your mount points are not put in correctly. For that reason the container is in a restart loop and retries to find the config.yaml.
If you post your docker run command that you used to start the node, we can start to get that sorted out.
# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point> <type> <options> <dump> <pass>
# / was on /dev/sda2 during installation
UUID=244477a3-3100-460f-a248-5194aa73854d / ext4 errors=remount-ro 0 1
# /boot/efi was on /dev/sda1 during installation
UUID=E139-E771 /boot/efi vfat umask=0077 0 1
/swapfile none swap sw 0 0
No. It is mapping of existing mount on your host to the container. It’s similar to mounting disks in the Linux, but not the replacement.
You should mount the disk to you host and then bind/map/mount it to the container.
So, please, make a mountpoint on your host: sudo mkdir /mnt/storj
Then add this line to the end of the /etc/fstab:
efa5d978dce8108719cc36d62e54bff9e09fd1d222cdf8320ea7a074dfd3d128
jamie@jamie-ubuntu:~$ sudo docker exec -it storagenode /app/dashboard.sh
Error response from daemon: Container efa5d978dce8108719cc36d62e54bff9e09fd1d222cdf8320ea7a074dfd3d128 is restarting, wait until the container is running
jamie@jamie-ubuntu:~$