Filesystem persistence for Docker workspace
I've just started experimenting with Coder and I'm using the Docker example template to create some workspaces. Our interntion is to move from local development on laptops to remote dev using Coder. However, I noticed that when my workspace is stopped automatically and then I restart it, any extra packages etc. I have installed are no longer there. E.g. if I do something like
I know I can add basic tools like this to the base Docker image for the workspace, but developers using workspaces are always going to be installing new things to try them out, changing configurations etc. When they restart a workspace after it was stopped, they will expect their workspace to be in the same state as it was when they last used it (just like it would be if they were using a physical laptop).
Is there any way to configure the workspace template so that the entire filesystem is persisted on a volume? Basically I want it to emulate having a physical dev machine that you can turn off and on again and retain the entire OS as-is. Perhaps this is something obvious you can configure in the tf file but I'm new to Terraform so I'm not sure how to go about it.
sudo apt install nanonanoI know I can add basic tools like this to the base Docker image for the workspace, but developers using workspaces are always going to be installing new things to try them out, changing configurations etc. When they restart a workspace after it was stopped, they will expect their workspace to be in the same state as it was when they last used it (just like it would be if they were using a physical laptop).
Is there any way to configure the workspace template so that the entire filesystem is persisted on a volume? Basically I want it to emulate having a physical dev machine that you can turn off and on again and retain the entire OS as-is. Perhaps this is something obvious you can configure in the tf file but I'm new to Terraform so I'm not sure how to go about it.
