Add link for starting containers on system boot
As mentioned in the comment; this behavior is different in Podman than how it is in Docker.
This commit is contained in:
parent
16a0dc1e20
commit
606a26a008
2 changed files with 9 additions and 1 deletions
|
|
@ -19,7 +19,11 @@
|
|||
containers.podman.podman_container:
|
||||
name: actual-server
|
||||
image: docker.io/actualbudget/actual-server:24.4.0
|
||||
restart_policy: on-failure # TODO: Doesn't restart containers on reboot for some reason...
|
||||
# TODO: Enable containers on boot
|
||||
# I expected podman containers to restart on boot with this policy but apparently the documentation specifically
|
||||
# states that they won't do this. There seems to be an involved workaround to get this to work whilst keeping the
|
||||
# containers "rootless". See this guide: https://linuxhandbook.com/autostart-podman-containers/
|
||||
restart_policy: on-failure
|
||||
publish:
|
||||
- 127.0.0.1:5006:5006
|
||||
volumes:
|
||||
|
|
|
|||
|
|
@ -40,6 +40,10 @@
|
|||
containers.podman.podman_container:
|
||||
name: pi-hole
|
||||
image: docker.io/pihole/pihole:2024.03.2
|
||||
# TODO: Enable containers on boot
|
||||
# I expected podman containers to restart on boot with this policy but apparently the documentation specifically
|
||||
# states that they won't do this. There seems to be an involved workaround to get this to work whilst keeping the
|
||||
# containers "rootless". See this guide: https://linuxhandbook.com/autostart-podman-containers/
|
||||
restart_policy: on-failure
|
||||
publish:
|
||||
# It seems we can't use authbind in combination with Podman, see: https://github.com/containers/podman/issues/13426.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue