![]() ![]() v /mnt/data/Documentaries:/data/Documentaries \ To create the container from the image: podman create \ What advantage would Podman have over Docker? I understand that Podman doesn’t have a daemon and that it runs the container in user mode, is that important?Īccording to the documentation, it looks like I would simply have to replace the word docker with podman to all my used commands: I run linuxserver/plex in a Docker container on Silverblue (non-docker compose). In this case, though, you shouldn’t need any of them. It’s more powerful, and since it’s a part of core podman, it will be less buggy than podman-compose (absolutely no offence intended to the devs). I’m glad someone is developing the podman-compose tool for simple existing docker-compose.yml setups, but when you need a multi-container setup, I would research the podman pod command to chain two or more containers together instead. If you need to access the file system after creation, you can use podman exec -it plex bash. Do you need this? (The plexinc/pms-docker container has a couple of different flags, you could modify that instead.) Also, I’m not sure what the restart flag does. But I’m not sure, try with them if you can’t make it work. I would probably try without the UMASK, PUID and PGID variables first, since you might not need it in a rootless container like podman. I don’t use Plex, so this is untested, but converted to podman run it would be something like this: podman run -it \ It should be easy to bypass it using podman run the first time (and then podman start plex subsequent times). If I’m reading the docs on the first docker hub link correctly, that docker-compose.yml file is only running one service anyway, so it doesn’t serve much of a purpose when a oneliner would suffice.
0 Comments
Leave a Reply. |