OCI image compatibility spec - FYI

2023-10-09 Thread Greg Wallace
Hi all, I have been trying to stay tuned in to all the efforts to get a native OCI runtime on FreeBSD. There are a lot of people interested in this and several efforts underway. In the course of listening in on some of the OCI community developer calls, I learned about this effort to create image

Re: OCI image compatibility spec - FYI

2023-10-09 Thread Doug Rabson
On Mon, 9 Oct 2023 at 13:51, Greg Wallace wrote: > Hi all, > > I have been trying to stay tuned in to all the efforts to get a native OCI > runtime on FreeBSD. There are a lot of people interested in this and > several efforts underway. > > In the course of listening in on some of the OCI communi

Re: OCI image compatibility spec - FYI

2023-10-09 Thread Greg Wallace
Hi Doug, I have followed your work with great interest, though I have to admit that, because I am not a developer or DevOps practitioner, my understanding is incomplete. I am in 100% agreement with you that the PR I shared is less important than the runtime spec. I just wanted to bring it to the

Re: OCI image compatibility spec - FYI

2023-10-09 Thread Doug Rabson
A while ago I drafted https://github.com/dfr/opencontainers-tob/tree/freebsd but neither I nor Samuel Karp had enough time to take this forward. Since then, we have resolved one of the trickier differences between the podman/buildah port and containerd/nerdctl around network configuration and I thi

[Bug 274007] IPSec asymmetric crypto broken

2023-10-09 Thread bugzilla-noreply
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=274007 --- Comment #3 from Shawn Anastasio --- I am able to reproduce this on -CURRENT on powerpc64le. With a debug kernel build, I'm hitting the following assertion when flooding an ipsec link between two VMs using ipsec3 with the net.inet.ipsec.