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

Should stop running containers before updating #59

Open
Thegaram opened this issue Oct 16, 2020 · 0 comments
Open

Should stop running containers before updating #59

Thegaram opened this issue Oct 16, 2020 · 0 comments
Labels
enhancement New feature or request

Comments

@Thegaram
Copy link

I started a local node, then a got prompted to update to v0.4.2, so I updated. When I wanted to run a local node again, I got this error:

> docker run -it --rm --name conflux-dev-node-0.6.3 -p 12535:12535 -p 12536:12536 -p 12537:12537 -v conflux-dev-node:/conflux-node -w /conflux-node --entrypoint conflux confluxchain/conflux-rust:0.6.3 --config default.toml
docker: Error response from daemon: Conflict. The container name "/conflux-dev-node-0.6.3" is already in use by container "5103ff323c978b903a50595466126a22a1c20b32cf57126aa58829925e08a270". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.

So I had to stop that container manually. Conflux Studio should stop all running containers before updating.

It would also be nice if Conflux Studio could handle such common Docker errors automatically, they are confusing for beginners who are not familiar with Docker.

@leonlianght leonlianght added the enhancement New feature or request label Oct 24, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants