Github messages for voidlinux
 help / color / mirror / Atom feed
From: lemmi <lemmi@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: Re: podman: add runit service
Date: Wed, 16 Mar 2022 05:14:26 +0100	[thread overview]
Message-ID: <20220316041426.L1a4NHr8otRXNmpKdjNEXvZRRdL7xTIoksKvQ1HCcEY@z> (raw)
In-Reply-To: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-36102@inbox.vuxu.org>

[-- Attachment #1: Type: text/plain, Size: 676 bytes --]

New comment by lemmi on void-packages repository

https://github.com/void-linux/void-packages/pull/36102#issuecomment-1068713331

Comment:
@the-maldridge yeah, I was thinking the same. 
I also had another look around. Seems like upstream suggests [this solution](https://github.com/containers/podman/blob/main/contrib/systemd/system/podman-docker.conf). They start `podman` with the default location, but provide a systemd config that creates a symlink from the `docker` default socket path to the `podman` socket path.
Maybe we could mimick that by providing a `podman` service with default options and optional config and a `podman-docker` service, that adds the symlink.

  parent reply	other threads:[~2022-03-16  4:14 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-03-11 21:43 [PR PATCH] " lemmi
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 [this message]
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=20220316041426.L1a4NHr8otRXNmpKdjNEXvZRRdL7xTIoksKvQ1HCcEY@z \
    --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).