docker: Error response from daemon: Ports are not available: exposing port TCP 127.0.0.1:14002 → 0.0.0.0:0: listen tcp 127.0.0.1:14002: bind: Only one usage of each socket address (protocol/network address/port) is normally permitted.
I’m getting this Error When running this docker Command
I have a node on this Pc. but am Trying to set other one up on docker. I know that’s my dashboard Address but how can I fix this so I can run multiple nodes on docker?
You need to use different port (the left part of mapping) for the second node on the same PC, i.e. -p 28968:28967/tcp -p 28968:28967/udp -p 127.0.0.1:14003:14002 -e ADDRESS=domain.ddns.net:28968
You also need to add port forwarding rules for TCP+UDP and this new port, i.e. 28968 to 28968 on your PC in my example.
Do not forget to add an inbound firewall rules for both TCP and UDP and this new port too.
See How to add an additional drive? - Storj Docs.
Also I hope that the source parameter of your --mount options are not empty and points to the correct locations for the second identity and the second disk.
I had the -p 28968:28967/TCP & UDP setting set up Right and my mount is all there, I was missing “-p 127.0.0.1:14003:14002 -e” Portion.
when I run the Docker I’m getting error codes in the logs and my Dashboard isn’t pulling up
023-11-06 08:41:49 Error: Error starting master database on storagenode: group:
2023-11-06 08:41:49 — stat config/storage/blobs: no such file or directory
2023-11-06 08:41:49 — stat config/storage/temp: no such file or directory
2023-11-06 08:41:49 — stat config/storage/garbage: no such file or directory
2023-11-06 08:41:49 — stat config/storage/trash: no such file or directory
2023-11-06 08:41:49 2023-11-06 15:41:49,775 INFO exited: storagenode (exit status 1; not expected)
2023-11-06 08:41:50 2023-11-06 15:41:50,751 WARN received SIGTERM indicating exit request
2023-11-06 08:41:50 2023-11-06 15:41:50,751 INFO waiting for storagenode, processes-exit-eventlistener, storagenode-updater to die
2023-11-06 08:41:50 2023-11-06T15:41:50Z INFO Got a signal from the OS: “terminated” {“Process”: “storagenode-updater”}
2023-11-06 08:41:50 2023-11-06 15:41:50,753 INFO stopped: storagenode-updater (exit status 0)
2023-11-06 08:41:51 2023-11-06 15:41:51,755 INFO stopped: processes-exit-eventlistener (terminated by SIGTERM)
My Storage Drive D:\ does have the correct path to the blobs, Temp, ECT. not sure what I did Wrong
if this node is never worked before and this is a new node, then you missed a one-time SETUP step (you should run it only once for the entire node’s life).
If it worked before, but stopped with these errors, you must not use the SETUP step, instead you need to check the path for data - it must point to the data location, where should be a config.yaml file and the storage subfolder.
