podman: containers are not started on boot
Nobody has claimed this yet.
- Dominant language
- Makefile
- Stars
- 4.6k
- Forks
- 4k
- Avg merge
- 3d 12h
- Merged PRs (30d)
- 134
Description
Package Name
podman
Maintainer
@oskarirauta
OpenWrt Version
SNAPSHOT
Steps to Reproduce
- start some container with Restart policy:
unless-stopped:
podman run imageID --detach --restart unless-stopped - reboot
Actual Behaviour
There are no started containers on boot:
$ podman container ls
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
$
Confirmation Checklist
- The package is maintained in this repository.
- I understand that issues related to the base OpenWrt repository or LuCI repository will be closed.
- I am reporting an issue for OpenWrt, not an unsupported fork.
Additional info:
The docs:
https://openwrt.org/docs/guide-user/virtualization/podman#podman_init_script
https://openwrt.org/docs/guide-user/virtualization/docker_host?s%5B%5D=podman#automation
The discussion:
https://forum.openwrt.org/t/guide-running-podman-containers-on-openwrt-24-10-2/
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start with the podman init-script documentation and the linked forum discussion, then reproduce the reported unless-stopped behavior across a reboot. Trace the package's boot startup entry point and verify that a container with that policy is running after boot; confirm the result with podman container ls.
Written by the indexing model from the issue text.
Assessment
- Domain
- devops, operating-systems
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 48/100