3 ms·
> Weird, they were for me. Were you using volumes? Currently a container's volumes are reset when the container is restarted. That's fixed in master. > Where
by dsissitka 13y ago
> Weird, they were for me.
Were you using volumes? Currently a container's volumes are reset when the container is restarted. That's fixed in master.
> Where do you get the modified id from?
In this case I just copied it from the container's command prompt. It's also available via docker ps -a:
$ docker run base sleep 1
$ docker ps -a
ID IMAGE COMMAND CREATED STATUS PORTS
041d889d7bd8 base:latest sleep 1 5 seconds ago Exit 0
$
- StavrosK 13y agoHmm, no, I wasn't using volumes. I was doing "docker ps", but didn't notice (or didn't know to use) an id, so I just did "docker run Ubuntu etc".
- StavrosK 13y agoApparently I don't know how to use docker. You are right, I was just starting the base image every time. Starting it creates a new container which you can find with "ps -a", and you can start/attach to it later the way you said. Thanks for the tip, I need to find a good tutorial or write one.