-
Notifications
You must be signed in to change notification settings - Fork 33
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
Add a guide for using podman quadlet files #103
Comments
i have no experience with Podman, and no time to verify any of this information. One way would be to add a community guide under https://komga.org/docs/community and we could reference that from https://komga.org/docs/installation/docker what do you think ? |
or if you maintain this information somewhere (gist or github repo) we could just add a link in https://komga.org/docs/community |
That seems reasonable. Also should note that the podman version that works with the quadlet files should also be mentioned with the guide since it works differently for different versions. |
do you want to take a dab at a PR ? you can start by just creating a simple md file in I think it would make sense to have a first section explaining how to run Komga only, and maybe a second one bundling Komga and Komf ? |
Yeah I'll try making a PR. I agree a section for just running komga first seems like a good idea. |
I've made a PR at #104. Let me know if there's anything I could do to improve it. |
I think it would be nice to have a guide with example quadlet files for people using podman.
Here's some examples based on the quadlet files I use to run komga and komf.
komga.pod
komga.container
See this post for the reason for adding 143 as a success exit code
komf.container
See this page for how to create podman secrets.
I have all three files above in
~/.config/containers/systemd/komga
directory. Then I runsystemctl --user daemon-reload
to generate the systemd services from the quadlet files. After that I just start thekomga-pod.service
withsystemctl --user start komga-pod.service
. If I wanted to start the komga pod when I boot up the server I could add the following tokomga.pod
The text was updated successfully, but these errors were encountered: