Node not starting after docker update

Node Operators troubleshooting
,
21

storagenode:alpha needs to be storagenode:beta

22

In the powershell:

ls E:\identity\storagenode
23

PS C:\Users\alex> ls E:\identity\storagenode

Directory: E:\identity\storagenode

Mode LastWriteTime Length Name

-a---- 8/2/2019 6:15 PM 546 ca.1564758906.cert
-a---- 8/2/2019 6:15 PM 1076 ca.cert
-a---- 8/2/2019 6:13 PM 241 ca.key
-a---- 8/2/2019 6:15 PM 1088 identity.1564758906.cert
-a---- 8/2/2019 6:15 PM 1618 identity.cert
-a---- 8/2/2019 6:13 PM 241 identity.key

PS C:\Users\alex>

24

Looks normal.
Please, try to reset the docker from the Docker desktop, then try to run the container again.

25

how do I reset it ? reinstall or what

26

Open docker desktop settings, click the “Reset” and select “Reset to factory defaults”

27

there is no reset option in my docker…

28

Right click on docker icon in your system tray, click Settings, on the left at bottom in the pop up you should see RESET.

29

I think Im going crazy

30

Is it docker Enterprise Edition or Community Edition?

31

comunity… …

32

Your not crazy I see the samething with mine.

33

I hate docker …

34

Right click and goto troubleshoot its in there now.

35

found it, thx, lets see

36

I reseted to factorry defaults and I still get the same error after accepting to share the drive

C:\Users\alex>docker run -d --restart unless-stopped -p 28967:28967 -e WALLET=“0xDCE74C111f64cD8Cf7aB9480d37E3128B58b8d97” -e EMAIL="alex@upload-drive.com" -e ADDRESS=“updrv.go.ro:28967” -e BANDWIDTH=“2000TB” -e STORAGE=“10TB” --mount type=bind,source=E:\identity\storagenode,destination=/app/identity --mount type=bind,source=E:,destination=/app/config --name storagenode storjlabs/storagenode:alpha
docker: Error response from daemon: invalid mount config for type “bind”: bind source path does not exist: /host_mnt/e/identity/storagenode.
See ‘docker run --help’.

any ideeas ?

37

Can you show your start command your using for docker? It looks like you maybe missing something

38

this ?

docker run -d --restart unless-stopped -p 28967:28967 -e WALLET=“0xDCE74C111f64cD8Cf7aB9480d37E3128B58b8d97” -e EMAIL="alex@upload-drive.com" -e ADDRESS=“updrv.go.ro:28967” -e BANDWIDTH=“2000TB” -e STORAGE=“10TB” --mount type=bind,source=E:\identity\storagenode,destination=/app/identity --mount type=bind,source=E:,destination=/app/config --name storagenode storjlabs/storagenode:alpha

39

You should be using the updated command

docker run -d --restart unless-stopped -p 28967:28967 -p 127.0.0.1:14002:14002 -e WALLET=“0xXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX” -e EMAIL="user@example.com" -e ADDRESS=“domain.ddns.net:28967” -e BANDWIDTH=“20TB” -e STORAGE=“2TB” --mount type=bind,source=“”,destination=/app/identity --mount type=bind,source=“”,destination=/app/config --name storagenode storjlabs/storagenode:beta

40

I’ve the same issue, except i’ve a problem of connection. I think the update has a serious and general problem for everyone, because the NAT of Docker doesn’t exist anymore, and Windows asked me to authorize the app for network, but even after that, and reboot, the same problem occurs. The problem is this update, I regret I upgraded too fast this one, since the others updates didn’t did bad thing.

I’m looking vpnkit-bridge, because its maybe a new process to authorize in the firewall… But I disabled all my firewall, and same problem occurs…

Can we securaly fall back in the previous version of Docker without losing the nodes ?