Docker container restarting repeatedly

Node Operators troubleshooting
,
1

I am getting repeated restarts of the docker container. This is a new node and my first on Linux.
Here are the lines from the syslog. Any assistance would be helpful.

Aug 17 18:56:36 proxy-primary kernel: [12969278.504942] docker0: port 1(vetha9b39ad) entered disabled state

Aug 17 18:56:36 proxy-primary kernel: [12969278.505034] veth2d5c3a5: renamed from eth0

Aug 17 18:56:36 proxy-primary networkd-dispatcher[729]: WARNING:Unknown index 113 seen, reloading interface list

Aug 17 18:56:36 proxy-primary kernel: [12969278.569528] docker0: port 1(vetha9b39ad) entered disabled state

Aug 17 18:56:36 proxy-primary systemd-networkd[677]: vetha9b39ad: Link DOWN

Aug 17 18:56:36 proxy-primary kernel: [12969278.575931] device vetha9b39ad left promiscuous mode

Aug 17 18:56:36 proxy-primary kernel: [12969278.575940] docker0: port 1(vetha9b39ad) entered disabled state

Aug 17 18:56:36 proxy-primary systemd-networkd[677]: rtnl: received neighbor for link ‘114’ we don’t know about, ignoring.

Aug 17 18:56:36 proxy-primary systemd-networkd[677]: rtnl: received neighbor for link ‘114’ we don’t know about, ignoring.

Aug 17 18:56:36 proxy-primary systemd-udevd[2762378]: veth2d5c3a5: Failed to get link config: No such device

Aug 17 18:56:36 proxy-primary networkd-dispatcher[729]: ERROR:Unknown interface index 113 seen even after reload

Aug 17 18:56:36 proxy-primary networkd-dispatcher[729]: WARNING:Unknown index 113 seen, reloading interface list

Aug 17 18:56:36 proxy-primary networkd-dispatcher[729]: ERROR:Unknown interface index 113 seen even after reload

Aug 17 18:56:36 proxy-primary systemd[2709993]: run-docker-netns-a84c7b586838.mount: Succeeded.

Aug 17 18:56:36 proxy-primary systemd[1]: run-docker-netns-a84c7b586838.mount: Succeeded.

Aug 17 18:56:36 proxy-primary systemd[2709993]: var-lib-docker-overlay2-433e784f93a9cd6c29225291b00275af0fa744a1a39c657ff46c205e1b8226de-merged.mount: Succeeded.

Aug 17 18:56:36 proxy-primary systemd[1]: var-lib-docker-overlay2-433e784f93a9cd6c29225291b00275af0fa744a1a39c657ff46c205e1b8226de-merged.mount: Succeeded.

Aug 17 18:56:36 proxy-primary systemd-udevd[2762378]: veth2d5c3a5: Failed to get link config: No such device

Aug 17 18:56:37 proxy-primary systemd-networkd[677]: docker0: Lost carrier

2

Perhaps you have to show your comands.
Seems like something with the network configuration didn’t work out.
Have you already tried to search on the world wide web? Since there are plenty reports on it… An have you updated the whole docker package and so on?

3

Its a brand new install of docker, so I would hope its latest.
Im running the script off of the storj installation proceedure.
Replacing the defaults with my specific values of course. Its
obviously a network issue based on the errors. I found some other people having a similar docker issue but no good answers so far

docker run -d --restart unless-stopped --stop-timeout 300
-p 28967:28967/tcp
-p 28967:28967/udp
-p 127.0.0.1:14002:14002
-e WALLET=“0xXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX”
-e EMAIL="user@example.com"
-e ADDRESS=“domain.ddns.net:28967”
-e STORAGE=“2TB”
–user $(id -u):$(id -g)
–mount type=bind,source=“”,destination=/app/identity
–mount type=bind,source=“”,destination=/app/config
–name storagenode storjlabs/storagenode:latest

4

On what platform are you?
How did you install docker?
Did you do any network adaptations to docker or your OS?

5

Ubuntu
Install Docker Engine on Ubuntu | Docker Documentation <— Procedure from here
No to network adaptations.
no firewall currently turned on

6

I actually usually use the convenience scripts, but that’s a side node in the discussion.

sudo docker run hello-world does work?
And OS fully updated?

7

Show the content of the log file for storagenode

1 Like
8

these looking wrong, where is the path?

1 Like
9

I think its redacted just like email, wallet and DDNS but let’s hear from OP :slight_smile:

10

This is the default script. I did not post my actual values.

11

The hello world script works fine, in answer to the question above. The issue appears to be with the virtual network interface.

Update: Found the issue, there was a misspelling in the path to the identity file in the startup script. Once I fixed that the node came right up. The error message in the syslog from docker was taking me down the wrong rabbit hole

2 Likes
12

Yes, usually you need to check the node’s log first and only then a syslog (or journalctl).