Documentation unclear regarding Docker

[ejohb]

Hi all,

I've just seen in the README that "Docker and containerized systems are not supported. Running Timeshift on such systems will have unpredictable results."

However, I've been using Timeshift on a Docker host seemingly without issue (yes, I've actually applied restore points in practice) because I was unaware of any issue. Since everything has been working for me, is this issue still even relevant?

If so, I'd like to suggest the following:

• The above README line should be clarified. Is the problem running on a Docker host - or inside a container? What is the nature of the problem? Can it be worked around?
• When going through the Timeshift on-boarding, a warning should appear if the Docker daemon is running.

[sskras]

I guess the original statement warns about dealing with /var/lib/docker directory on the host: https://stackoverflow.com/questions/76280433/how-to-get-docker-to-read-var-lib-docker-correctly

If docker is stopped, my guess is that reading the directory is going to avoid corruption of logical structure in the data files, which otherwise changes so quickly that even FS snapshots doesn't guarantee consistent state of the files: https://community.sisense.com/t5/knowledge/relocating-var-lib-docker-directory/ta-p/18596

[mkindred]

My limited understanding is that docker (host) uses bind mount points, which fools (fooled) timeshift into changing its snapshots directory. It seems that this was mitigated back in 2018 in the previous repository, but I haven't tried it for myself.

It does look as though that commit is in this repository.

I agree that the README should be updated and clarified.