Can I persist docker container?

[am009]

In my use case, we are not familiar with changing template each time, so I would like to keep the container there when stopping, and restart the container when starting, instead creating a new one.
I tried to add lifecycle { ignore_changes = all } to container, but the workspace cannot restart after a stop.

[matifali]

You should look at mounting volumes to persist your workspace directories. See this template for example.

https://github.com/matifali/coder-templates/blob/main/deeplearning/main.tf

[am009]

I know that the usual way is to mount volumes to persist workspace, and we are using it. but I still want the possibility to keep the container, so that I can use it like an VM, and use the most basic template for everything, although it might cost more storage.

[matifali]

Try setting count = 1 for docker_container resource.
This will prevent coder from deleting the container.

[am009]

I tried it right now, but it doesn't seem to work. When I stop the workspace, the container doesn't stop at all, and I can still connect to it. When I restart the workspace, the container is still recreated. (My test file under root disapperred, and the container ID changed.)

[am009]

I added lifecycle { ignore_changes = all } (docs) for docker_container resource. Then I stop the workspace, the code server seems to be stopped (I cannot connect to it.), the container still doesn't stop. Then I manually stop the container. Then restart the workspace, the container was started as expected (not recreated).

BUT, if I don't stop the container after stopping the workspace, and start the workspace, wired things happen, unable to connect (the ui keeps loading, ps -aux in container shows two code-server instances).

Probably, coder should stop all container when stopping a workspace? By the way, I see nothing related to stopping a container in terraform docs. Probably terraform simply doesn't support stopping a container? Can anyone tell me is that correct?

[matifali]

I am not sure, but there are some options relating to stopping a container here, https://registry.terraform.io/providers/kreuzwerker/docker/latest/docs/resources/container
if you search for stop keyword.

[am009]

I got a feeling that the stop in the doc is only used for (before) destroy.

[matifali]

https://discuss.hashicorp.com/t/docker-provider-restart-stopped-containers-instead-of-recreating/7365
Something similar to what you are looking for. But no responses.

[am009]

Thanks. Probably this is the case.

[matifali]

You cannot persist a container on workspace stop. Even if you somehow prevent terraform from destroying it it will be recreated/replaced on the next workspace restart.
For persistence you should mount volumes to the directories you need.