From: paul via <help-guix@gnu.org>
To: Aleksej <lesikedelweiss@disroot.org>, Guix Help <help-guix@gnu.org>
Subject: Re: OCI containers
Date: Sat, 21 Dec 2024 02:06:20 +0100 [thread overview]
Message-ID: <0dde3080-ebe3-4b2c-a1aa-e580344d5804@autistici.org> (raw)
In-Reply-To: <DD00C36E-8802-4CA7-8072-544A8B8D3AAC@disroot.org>
Hi Lesik,
On 12/20/24 00:14, Aleksej via wrote:
> 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?
It definitely can :) I'm working on an oci-service-type over at gocix
[0], which will deprecate the oci-container-service-type. It is
introducing a configurable OCI runtime supporting rootless Podman and
Docker, and the ability to provision networks and volumes. It still
isn't well tested as I was waiting for rootless Podman to get into Guix
mainline before focusing on it. Hopefully during the end of the year
break I'll be able to test it better and send it upstream. You are
welcome to try it [1] and open issues if you find problems. It is not
yet very well documented but you can find API documentation here [2].
> 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?
There is no specific reason besides being the easiest way I was able to
find to get Podman up and running. If you could make the firewall
backend configurable it would be awesome imho.
hope this helps,
giacomo
[0]:
https://github.com/fishinthecalculator/gocix/blob/main/modules/oci/services/containers.scm#L768
[1]:
https://github.com/fishinthecalculator/gocix?tab=readme-ov-file#configure
[2]: https://github.com/fishinthecalculator/gocix/tree/main/doc#OCI-Service
prev parent reply other threads:[~2024-12-21 1:07 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 23:14 OCI containers Aleksej via
2024-12-21 1:06 ` paul via [this message]
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=0dde3080-ebe3-4b2c-a1aa-e580344d5804@autistici.org \
--to=help-guix@gnu.org \
--cc=goodoldpaul@autistici.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).