From: lemmi <lemmi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [PR PATCH] podman: add runit service
Date: Fri, 11 Mar 2022 22:43:34 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36102@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 542 bytes --]
There is a new pull request by lemmi against master on the void-packages repository
https://github.com/lemmi/void-packages podman
https://github.com/void-linux/void-packages/pull/36102
podman: add runit service
[Upstream Systemd service](https://github.com/containers/podman/blob/v4.0.2/contrib/systemd/system/podman.service.in) doesn't do anything special. `--time=0 unix:///var/run/docker.sock` is required, since we don't have socket activation.
A patch file from https://github.com/void-linux/void-packages/pull/36102.patch is attached
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: github-pr-podman-36102.patch --]
[-- Type: text/x-diff, Size: 1660 bytes --]
From d3427f8b1003f7162d334b0df0ae82a06018890d Mon Sep 17 00:00:00 2001
From: lemmi <lemmi@nerd2nerd.org>
Date: Fri, 11 Mar 2022 22:37:26 +0100
Subject: [PATCH] podman: add runit service
---
srcpkgs/podman/files/podman/log/run | 1 +
srcpkgs/podman/files/podman/run | 3 +++
srcpkgs/podman/template | 3 ++-
3 files changed, 6 insertions(+), 1 deletion(-)
create mode 120000 srcpkgs/podman/files/podman/log/run
create mode 100644 srcpkgs/podman/files/podman/run
diff --git a/srcpkgs/podman/files/podman/log/run b/srcpkgs/podman/files/podman/log/run
new file mode 120000
index 000000000000..3a5b4a586051
--- /dev/null
+++ b/srcpkgs/podman/files/podman/log/run
@@ -0,0 +1 @@
+/usr/bin/vlogger
\ No newline at end of file
diff --git a/srcpkgs/podman/files/podman/run b/srcpkgs/podman/files/podman/run
new file mode 100644
index 000000000000..c98a70437f84
--- /dev/null
+++ b/srcpkgs/podman/files/podman/run
@@ -0,0 +1,3 @@
+#!/bin/sh
+
+exec podman --log-level info system service --time=0 unix:///var/run/docker.sock
diff --git a/srcpkgs/podman/template b/srcpkgs/podman/template
index c719e4ca6057..b202bb9823d6 100644
--- a/srcpkgs/podman/template
+++ b/srcpkgs/podman/template
@@ -1,7 +1,7 @@
# Template file for 'podman'
pkgname=podman
version=4.0.2
-revision=2
+revision=3
build_style=go
go_import_path="github.com/containers/podman/v4"
go_package="${go_import_path}/cmd/podman ${go_import_path}/cmd/rootlessport"
@@ -34,4 +34,5 @@ post_install() {
vendor/github.com/containers/common/pkg/config/containers.conf \
>containers.cgfs.conf
vinstall containers.cgfs.conf 644 usr/share/containers containers.conf
+ vsv podman
}
next reply other threads:[~2022-03-11 21:43 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-11 21:43 lemmi [this message]
2022-03-11 23:15 ` [PR REVIEW] " CameronNemo
2022-03-12 11:47 ` lemmi
2022-03-13 0:52 ` CameronNemo
2022-03-13 0:58 ` lemmi
2022-03-14 15:58 ` leahneukirchen
2022-03-16 3:58 ` the-maldridge
2022-03-16 4:14 ` lemmi
2022-03-16 14:38 ` leahneukirchen
2022-03-20 23:39 ` [PR PATCH] [Updated] " lemmi
2022-03-20 23:40 ` lemmi
2022-03-27 23:16 ` the-maldridge
2022-03-27 23:26 ` CameronNemo
2022-03-28 0:11 ` Duncaen
2022-03-28 14:36 ` [PR PATCH] [Merged]: " lemmi
2022-03-28 14:36 ` lemmi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36102@inbox.vuxu.org \
--to=lemmi@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).