#FreeBSD
Don't be too harsh ...
$ freebsd-version -kru
11.2-RELEASE-p8
11.2-RELEASE-p8
11.2-RELEASE-p8
$ uptime
2:25PM up 2600 days, 5:06, 2 users, load averages: 0.31, 0.24, 0.25
yOm
@y0m
- 20 Followers
- 48 Following
- 33 Posts
FreeBSD; Developer: C, Go, Rust, Zig; Gamer. Hominem te esse memento
@Skippythekangoo Les résultats de l'usage m'intéresse quelques soient les résultats, et si tu souhaites les partager (bien sûr) 😄
@[email protected] yes I could manage doing the same in a bastille jail adding some parameters, they may not be all usefull but it covers well :
allow.extattr allow.chflags allow.mount
allow.extattr allow.chflags allow.mount
@[email protected] the command I'm using is :
buildah from --storage-driver=vfs ghcr.io/freebsd/freebsd-runtime:15.0
The error I'm getting:
https://yom.iaelu.net/podman/buildah-from-trace.txt
@[email protected] yes, this was my first move, I got this one OK with containers creation hooks and jail -vm name={containername} allow.extattr ...
My problem comes after that first move :)
My problem comes after that first move :)
Hello #FreeBSD fellows.
I've been trying for a few days to use `buildah from ...` inside a freebsd-runtime:15.0 podman container. I could manage to work around the `extattr` using hooks, but I'm still getting stopped a 'operation not permitted' error, even looking buildah's code, or using truss for errors before the problem occurs.
Ofc, it's working directly on the host.
But I guess I just wanted to try to build freebsd images from containers triggered by CI in forgejo.
Any clue or advice?
I've been trying for a few days to use `buildah from ...` inside a freebsd-runtime:15.0 podman container. I could manage to work around the `extattr` using hooks, but I'm still getting stopped a 'operation not permitted' error, even looking buildah's code, or using truss for errors before the problem occurs.
Ofc, it's working directly on the host.
But I guess I just wanted to try to build freebsd images from containers triggered by CI in forgejo.
Any clue or advice?
@BastilleBSD production configuration files that should NOT be there, because I checked just in case before the no return point :)
@gumnos the #freebsd handbook seems to be specific about VNET jails, you've got to create a bridge, and use epair. Not sure you can use another way around, or at least for a time you could also use the netgraph driver for this... but I haven't seen a lot about that. @BastilleBSD uses PF rules to enable routing outside the host.
Hope you'll find the configuration you arr looking for.
Hope you'll find the configuration you arr looking for.
My tries on #FreeBSD #Containers using #Podman:
https://yom.iaelu.net/2025/11/2025-11-09-freebsd-containers/
https://yom.iaelu.net/2025/11/2025-11-09-freebsd-containers/
FreeBSD Containers using Podman
Table of Content Some contextal informations /etc/pf.conf and sysctls Testing configuration… Emerged problem from the PF+sysctl configuration Some contextual informations As everytime I’m trying myself on posting on this blog, I’ll take some time to try to put some context around my writings… Some of you may known, there has been some works for now over a few years on FreeBSD to try to give “Containers” (Docker, Podman, …) to its users. I’ve been watching its evolution from my point of view, sometimes interesting and sometimes I was wondering if this subject was going anywhere.