Replies: 1 comment 2 replies
-
This is not an issue really related to Semaphore but generally to podman. For mounting volumes your got to add :Z to get it writable. |
Beta Was this translation helpful? Give feedback.
2 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I'm trying to get a nice setup of Caddy running in a container managed with Podman. I can get it running but I have some issues with folder permissions.
With default setup if I create
semaphore-data
folder and map it to/etc/semaphore
, add config.json etc the process in a container can't use it.If I don't create those in advance those are getting added upon container creation. But they belong to user
232070
... which is also problematic if I want to add my own config file / edit existing one.If I create those advance and in
compose.yaml
I specify UID, GUID to be the same as user starting the containers Semaphore fails as it can't write to/tmp/semaphore
,/home/semaphore
(and maybe some other, but I've just started testing).For the time being I've mapped those folders in the volumes section. Is there a better / cleaner approach?
Beta Was this translation helpful? Give feedback.
All reactions