Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Containers stopped, can't start again #5

Closed
jpmeijers opened this issue Jan 3, 2022 · 0 comments
Closed

Containers stopped, can't start again #5

jpmeijers opened this issue Jan 3, 2022 · 0 comments

Comments

@jpmeijers
Copy link

After being confused why my gateways aren't forwarding packets, I logged into my server to check.

docker-ps indicates the containers are not running anymore.

When trying to start them again, I get an error:

$ ./run.sh -c /mnt/Data/HeliumGatewayRS/eui-<redacted-a>
Error response from daemon: No such container: helium-rs-mnt-Data-HeliumGatewayRS-eui-<redacted-a>
Error: No such container: helium-rs-mnt-Data-HeliumGatewayRS-eui-<redacted-a>
Unable to find image 'gateway-rs:latest' locally
docker: Error response from daemon: pull access denied for gateway-rs, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.
$ ./run.sh -c /mnt/Data/HeliumGatewayRS/eui-<redacted-b>/
Error response from daemon: No such container: helium-rs-mnt-Data-HeliumGatewayRS-eui-<redacted-b>
Error: No such container: helium-rs-mnt-Data-HeliumGatewayRS-eui-<redacted-b>
Unable to find image 'gateway-rs:latest' locally
docker: Error response from daemon: pull access denied for gateway-rs, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
See 'docker run --help'.

It seems like my docker instance deleted the gateway-rs image, and stopped the two running containers.

Building the image again using $ docker build -t gateway-rs ., and then executing the run commands works.

I believe what happened was my server did a software update this morning, and also updated the Docker service. I believe this must be the cause for the stopped containers and deleted images.

This is not an issue with this project, but leaving this issue here for future reference.

My containers that are run by Docker Compose were unaffected by the Docker update.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant