Autostart pod on system boot (#1561)

* Autostart pod on system boot

* ci: fix pre-commit

---------

Co-authored-by: Revant Nandgaonkar <revant.one@gmail.com>
This commit is contained in:
Amanuel Elhanan
2025-02-04 16:18:44 +03:00
committed by GitHub
parent 8cf986b855
commit 56e1da3f37

View File

@@ -88,6 +88,29 @@ Podman (the POD MANager) is a tool for managing containers and images, volumes m
- `bench new-site myerp.net --mariadb-root-password 123456 --admin-password 123123` - `bench new-site myerp.net --mariadb-root-password 123456 --admin-password 123123`
- `bench --site myerp.net install-app erpnext` - `bench --site myerp.net install-app erpnext`
## Autostart pod
- Systemd is the best option on autostart pods when the system boots. Create a unit file in either `/etc/systemd/system` [for root user] or `~/.config/systemd/user` [for non-root user]
```ruby
[Unit]
Description=Podman system daemon service
After=network-online.target
[Service]
#User=
#Group=
Type=oneshot
ExecStart=podman pod start POD_NAME
[Install]
WantedBy=default.target
```
**Note:** Replace POD_NAME with a created pod name while creating a pod. This is a basic systemd unit file to autostart pod, but multiple options can be used, refer to the man page for [systemd](https://man7.org/linux/man-pages/man1/init.1.html). For better management of containers, [Quadlet](https://docs.podman.io/en/v4.4/markdown/podman-systemd.unit.5.html) is the best option for ease of updating and tracing issues on each container.
## Troubleshoot ## Troubleshoot
- If there is a network issue while building the image, you need to remove caches and restart again - If there is a network issue while building the image, you need to remove caches and restart again