-
Notifications
You must be signed in to change notification settings - Fork 26
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
Permission issues for rootless container running with Podman #24
Comments
Thanks for reporting this issue, I do reproduce it locally and will do some research and fix it. |
@dmarcoux Please try the latest image ( |
Thank you @daya0576 for having a look. This is working now! |
I think my issue is related to this one, but updating to 0.3.5 did not solve the issue for me. I'm running the container on a NAS and after updating to the latest image today, I am seeing errors on startup. Unfortunately I do not know which specific tag I was upgrading from, it was the latest tag pulled about 3 weeks ago.
Here are the permissions:
|
@adamjt Thanks for reaching out, here is the root cause of this permission issue: #23
Please try these two options below to fix this issue: Option1: Update the permission of the volumn # Step1: Find current container user
$ docker run --rm daya0576/beaverhabits:0.3.5 cat /etc/passwd | id -u
1000
# Step2: Change folder permissions and ownership
$ sudo chown -R 1000 .user Option2: Running Docker containers as current host user docker run -d --name beaverhabits \
-u $(id -u):$(id -g) \
... |
Thank you, I apologize for reopening the wrong issue. After applying the fix I am back to tracking habits!
|
You're welcome! Glad to hear that this solution is working for you. |
Hello,
Thank you for beaverhabits 🙂!
I am running the application in a rootless container with Podman. I set the user and group of the container to the Podman user. As for the host path which is mounted as a volume, its owner is also the same Podman user. This setup works for other applications on my server.
Even with the changes from #18, I am still having permission issues.
This is what I get:
I believe the issue is that
/app
still belongs tonobody:root
as we can see here from within the container:It should instead be just like
/app/.user
(again from within the container):The text was updated successfully, but these errors were encountered: