--home: some configuration in deepin control center is lost. about dockerfile-x11docker-deepin

[hongyi-zhao]

BTW, the dirty and quick workaround for saving container's changes, say, --keepcache and docker commit should can persevere all user configurations, in case all other methods failed. But as you have told, it's not the suggested way and not a good practice for production environment.

[mviereck]

--keepcache and docker commit should can persevere all user configurations

If it does, deepin would not store its configuration in HOME. That would be wrong behaviour.

[hongyi-zhao]

If it does, deepin would not store its configuration in HOME. That would be wrong behaviour.

It seems that I'm still not understanding the data persistence mechanism of docker to a decent degree. Could you please give me some more detailed explanations on your above assertion?

[mviereck]

Basically it is simple:
It is standard that applications store user configurations in HOME.
x11docker provides option --home to preserve this folder on host.
That's all.

data persistence mechanism of docker

docker also provides so called "docker volumes" for persistent data storage. x11docker does not use this possibility (except you provide a docker volume with --home=volumename).

[hongyi-zhao]

Do you mean the current used method is based on bind mounts if the supplied argument is not a volumename?

[mviereck]

Yes, with docker option --volume. Compare the shown docker command if you run x11docker with option --debug.

[mviereck]

It seems o be a deepin issue that a few configurations in its control center are not stored. Closing issue because it is not caused by x11docker or the image build process.