New docker update error

805b99e893b0a14bc694 · January 25, 2020, 1:15pm

21.01.20 updated to docker desktop v 2.2.0.0 (42247)
every day had errors since

Error response from daemon: Bad response from Docker engine
Error response from daemon: open \.\pipe\docker_engine_linux: The system cannot find the file specified.
Error: failed to start containers: storagenode
error unrecoverable

What I did: uninstall new version of docker desktop and install previous 2.1.0.5

When I start storj node: Error response from daemon: invalid mount config for type “bind”: invalid mount path: ‘/app/identity’.

Error response from daemon: invalid mount config for type “bind”: stat /host_mnt/c/Users/tortu/AppData/Roaming/Storj/Identity/storagenode: transport endpoint is not connected

What should I do to fix it?

deathlessdd · January 25, 2020, 2:15pm

Id recommend moving to Windows GUI as the new docker update has caused numerous issues with running a node.

But we can try to get it running again have you tried removing the container and starting a new one?
If so what is your starting command for docker?

805b99e893b0a14bc694 · January 25, 2020, 2:31pm

It was running without problems since June 2019 and I’m out of date what to do

What should I do to "removing the container and starting a new one " ?

deathlessdd · January 25, 2020, 2:35pm

Run the command docker rm storagenode, Visit https://documentation.storj.io/setup/cli/storage-node to get the newest updated docker start command.

805b99e893b0a14bc694 · January 25, 2020, 2:40pm

C:\Users\tortu> docker pull storjlabs/storagenode:beta
beta: Pulling from storjlabs/storagenode
no matching manifest for windows/amd64 10.0.18362 in the manifest list entries

It was storagenode: alpha before

805b99e893b0a14bc694 · January 25, 2020, 2:55pm

I’ll be back tomorrow, going to night shift

Alexey · January 25, 2020, 5:34pm

Please, switch the docker back to Linux containers

805b99e893b0a14bc694 · January 26, 2020, 11:42am

Great advice Alexey, it’s running again. Thanks