Now what it does is - it reads image - move image to temp folder, compress it, copy back to its original location.
All goes well as I have started it with $UID as mentioned in your post.
However, let us say now the machine is restarted - somehow $UID becomes a root.
If you have observed the same problem? After restart - some images I uploaded are now compressed with the root user and not www-data as originally intended.
Any way without export UID?
env UID=${UID} GID=${GID} docker-compose upwould work without export UID, I suppose!Hi, if I do this, on restart (if I have docker always restart) permission is lost on system boot. Hence, this isn't a good way to do it.
Hi Varun,
Oh really? I don't have such experiences, as file permission usually doesn't change on system boot.
Hi
Let us say that you have a docker container which will keep creating files with some logic - in my case it is compressing the images.
I have written a blog for the docker I have added to a tool:
Lossless Image Compressions using Docker
Now what it does is - it reads image - move image to temp folder, compress it, copy back to its original location.
All goes well as I have started it with $UID as mentioned in your post.
However, let us say now the machine is restarted - somehow $UID becomes a root.
If you have observed the same problem? After restart - some images I uploaded are now compressed with the root user and not www-data as originally intended.
Sorry for my slow response.
I didn't investigate the problem deeply, and moving files to /tmp or such directory, and restart the machine.
Actually I recently don't use Docker on Linux with daily development. In production we don't store data to disk so don't care about the permissions.