We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
how can I perform an autostart via systemd
The text was updated successfully, but these errors were encountered:
rough untested(!) draft:
podman
/etc/systemd/system/systemctl-mqtt-podman-container.service
[Unit] After=dbus.socket Requires=dbus.socket [Service] Type=notify NotifyAccess=all ExecStartPre=/usr/sbin/apparmor_parser /somewhere/docker-apparmor-profile ExecStart=/usr/bin/podman run --cidfile %t/%n.ctr-id \ --rm --detach --sdnotify conmon --log-driver journald \ --name systemctl_mqtt \ -v /var/run/dbus/system_bus_socket:/var/run/dbus/system_bus_socket:rw \ --hostname %H --userns host --user 0 \ --security-opt no-new-privileges --security-opt apparmor=systemctl-mqtt \ docker.io/fphammerle/systemctl-mqtt:0.5.0-amd64@sha256:34dcb878dbd66315de6fbf97ceb29e8fec549b7269c6c828c4c889a54a091f14 \ systemctl-mqtt ... ExecStop=/usr/bin/podman stop --cidfile %t/%n.ctr-id ExecStopPost=/usr/bin/podman rm --cidfile %t/%n.ctr-id ExecStopPost=rm %t/%n.ctr-id [Install] WantedBy=multi-user.target
sudo systemctl daemon-reload
sudo systemctl enable systemctl-mqtt-podman-container.service
sudo systemctl start systemctl-mqtt-podman-container.service
Sorry, something went wrong.
No branches or pull requests
how can I perform an autostart via systemd
The text was updated successfully, but these errors were encountered: