-
Notifications
You must be signed in to change notification settings - Fork 35
Add freebsd dockerfile to be used with podman #296
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
|
pita nitpick: is there a specific reason to use your OCI images as opposed to the official ones? see https://hub.docker.com/r/freebsd/ or https://github.com/orgs/freebsd/packages |
I changed it to use this one. The reason was, that ghcr.io doesn't work on my test machine since it doesn't support ipv6 and I wasn't aware that it's available on docker.io as well. |
|
does this need podman to build the podman image too or can we just use buildx and distribute it officially? |
I don't know if that works, have only tried podman, as this runs natively on FreeBSD. |
|
is there a hoster that can spin up freebsd instances on demand? so we can integrate it in our test workflow? |
None that I'm aware of. I am using a static freebsd woodpecker-agent on Hetzner-Cloud with with local backend for such things. Maybe this can be adapted here. However, the instance is not build on demand since there's no freebsd image for this available there, so I'm using a snapshot I made earlier. have a look. I am not aware of any other way to do these kind of things with freebsd. But for github there's a FreeBSD image available which is basically a linux image running FreeBSD in qemu. Maybe that would be something for you? Repo is here, but it didn't work for my testcase on codeberg/woodpecker. |
I don't know if this is on-demand FreeBSD on Azure has nothing recent AWS has a FreeBSD 14 image from the FreeBSD Foundation along with FreeBSD 15 with ZFS |
This PR adds a new dockerfile for FreeBSD to be used with
podman build. A section in the README.md has been added.I am not sure if the Dockerfile is correct yet, please refer to #295.