New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Docker: Set explicit HOME env for Darktable & RawTherapee #1525
Comments
Yes, please. I've recently added an explicit workdir value for this, not sure if setting HOME is better? Can you test if the new docker-compose.yml files in our develop branch work for you? |
Note we're on vacation until later this week. |
Ok I finally finished indexing my photos, looks great! So after that I checked with
It seems it is pretty common problem, when try to use custom user inside container. In my case in docker-compose I use:
so that will be the user/group in which context rawtherapee-cli and darktable-cli will operate. However this user(id/gid) is not known inside container:
so also there is no HOME dir for this user, and when rawtherapee-cli or darktable-cli will try create some configuration files, they will try to do it in "/" dir where only root can do this. In my case I populate HOME env variable set to ' /photoprism' which have permissions allowing to create files for everyone:
including the user which I pass as in docker-compose:
|
May cause issues with multi-stage builds.
Seems setting an explicit |
Causes caching / performance issues.
It seems that |
Just moved to the bottom, so all user related parameters are in one place: services:
photoprism:
environment:
## Run as a specific user, group, or with a custom umask (does not work together with "user:")
# PHOTOPRISM_UID: 1000
# PHOTOPRISM_GID: 1000
# PHOTOPRISM_UMASK: 0000
HOME: "/photoprism"
## Start as a non-root user (see https://docs.docker.com/engine/reference/run/#user)
# user: "1000:1000" |
Ah, I was looking in https://github.com/photoprism/photoprism/blob/develop/docker-compose.yml. |
The development environment is different, yep. |
Hi,
I see in logs for all my raw files:
I run photoprism using below docker compose:
Both dartable-cli and rawtherapee-cli return errors in interactive mode:
I checked that HOME dir was set to '/' this is where above commands tries to create files, but '/' belongs to root so it can't create it there:
I changed HOME variable to point to '/photoprism' dir which allow me to use both commands:
On the end I extended my docker compose file with HOME: "/photoprism" in env section and conversion is working now.
Maybe it is worth to extend sample docker compose file with above information?
The text was updated successfully, but these errors were encountered: