unofficial mirror of help-guix@gnu.org 
 help / color / mirror / Atom feed
From: Aleksej via <help-guix@gnu.org>
To: Guix Help <help-guix@gnu.org>
Subject: OCI containers
Date: Fri, 20 Dec 2024 01:14:36 +0200	[thread overview]
Message-ID: <DD00C36E-8802-4CA7-8072-544A8B8D3AAC@disroot.org> (raw)

Hi,

I’m currently trying to migrate my server to the Guix System, but I’m encountering some issues with OCI containers. Is there a way to run them as a Shepherd service while using Podman and nftables? I know about the oci-container-service-type, but it depends on Docker and iptables, both of which I dislike due to their design. Perhaps the oci-container-service-type could be abstracted from its backend so that it supports both rootless Podman and Docker?

Also, why does the rootless-podman-service-type depend on iptables? Our netavark version has complete nftables support, so maybe we could add an option to choose between iptables and nftables?

I’m willing to write the necessary code if required, but I’d like to hear some advice first.

Best regards,
Lesik Edelweiss

             reply	other threads:[~2024-12-19 23:15 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-19 23:14 Aleksej via [this message]
2024-12-21  1:06 ` OCI containers paul via

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

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=DD00C36E-8802-4CA7-8072-544A8B8D3AAC@disroot.org \
    --to=help-guix@gnu.org \
    --cc=lesikedelweiss@disroot.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 read-only IMAP folder(s) and NNTP newsgroup(s).