view the rest of the comments
Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
There are a few ways around it. The simplest is to add the
--privileged
option.The more secure method with podman is by specifying a user (ex
-u 10001:10001
) from your extended subuid:subgid range after your full and proper setup of rootless podman :-)Then instead of
chown
you'll want to use the oddly namedpodman unshare
tool to automatically set the permissions of the host directory. You would then want to start your service withsystemctl --user
instead ofsudo systemctl
Okay so I've done these steps (it seems rootless podman have been setup by Rocky automatically):
privatenoob:100000:65536
2.:Changed ExecStart to this:
ExecStart=podman run --name=radarr -u 100000:65536 -p 7878:7878 -v radarr-config:/config -v /home/privatenoob/media/storage1/Filmek:/data --restart unless-stopped lscr.io/linuxserver/radarr:latest
3.:
podman unshare chown -R 100000:65536 /home/privatenoob/media/storage1/Filmek/
Unfortunately unsharing gave me invalid arguments.
chown: changing ownership of '/home/privatenoob/media/storage1/Filmek/': Invalid argument
I have tried by leaving the -e PUID=1000 parts on but those didn't work either. Yeah and I'm using systemctl --user. Thanks for your help!
Ah! I think I see the confusion.
This denotes the range of subuids that are available to your user.
This part specifies two things ([UID]:[GID]) even though it's the same syntax as the earlier part that specifies one range :)
I suspect what you will want to do is use the following:
Then we can specify that the user in the container can match the user (UID) we specified above:
As a note, if you copy/pasted that ExecStart line, you might have gotten the invalid argument error because you entered
100000
(outside of your subuid range, i.e. >65536) instead of10000
.There's a nice guide that gives a great walkthrough. I'll dig through my bookmarks and add it here when I get some time.
Hope this helps!