Can I connect back to a container after changing the compose file?

General
1

I messed up… I had a lot of stuff configured in a Z-Wave JS UI container on one pi, mad a few changes to the Docker-Compose file, and now I can’t get it up and running again, so I can do a backup of what I have done and get it to the Pi where it’s actually going to reside. :face_with_spiral_eyes: My own stupid mistake, but can I correct it? When I tried to start up the original container I get:

docker compose up
[+] Running 0/0
⠋ Container Z-Wave-JS-UI Creating 0.0s
Error response from daemon: Conflict. The container name “/Z-Wave-JS-UI” is already in use by container “f64b15562dd105e9997dfba1e7b21c989b767c187f420ea7f22d597eb092c57c”. You have to remove (or rename) that container to be able to reuse that name.

But the original container is not running, it doesn’t show up on docker ps and I am certain about that, so I can’t understand why it won’t work. Can I do anything to get back into that container to backup the stuff I had configured? Is it possible that Docker is in some way trying to start the container in the background even if I have set restart to no in the Docker Compose file?

2

Never mind, I th ink I have double blown it. I tried docker container stop on the original container because docker ps -a showed that it was trying to start, and when I started the docker compose file again, all the customization was gone. :frowning:

3

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.