RE: https://mastodon.social/@lobsters/116245208451246991

daemonless – <https://daemonless.io/> @ahze

― a collection of FreeBSD-native OCI images that run directly on the FreeBSD kernel. It combines the power and security of Jails with the modern container ecosystem—compatible with Podman, AppJail, or any OCI-compliant runtime. No Linux virtual machines or overhead required.

#OCI #FreeBSD #jails #containers #PodMan #AppJail #Linux

― via <https://www.reddit.com/r/selfhosted/comments/1pw7kbs/introducing_daemonlessio_native_freebsd_oci/> (2025),<https://www.reddit.com/r/freebsd/comments/1rw9o7h/daemonless_native_freebsd_oci_containers_jails/> (March 2026), and Lobsters.

There's one last thing I need to get my head around with respect to using FreeBSD jails as a replacement for docker/podman.

I generally configure containers as totally ephemeral. Any data or individual files that a container uses, and that I care to keep, resides outside the container. It is linked inside via volumes defined in the run shell script or compose file. In some cases even dumb things like root's .bashrc gets linked in so that nuking a container doesn't lose the shell history the next time something needs hand fettling (mediawiki, maintenance scripts, composer, bootstrap, and friends - yes, needs more automation).

Any time a container gets restarted, step one may be to delete the container (and associated volumes it creates), re-pull latest and instantiate fresh. This is pretty typical for Jellyfin for example.

Also, working this way means that the entire backup process can exist outside the container volumes and nothing redundant in /var/lib/docker needs to get backed up.

Anyway, I need to figure out how to achieve something similar under FreeBSD jails. I'm assuming there is something in ZFS that provides a similar type of functionality during jail startup but haven't dug into it yet.

Then there's the 'correct' and easy way on how to upgrade the software inside a jail (os components and services the container runs) that needs experimentation on my side. Some scripting to do.

Jails seem much more elegant but there is lot of old cruft and 'finger memory' to work around. Ha. A lot of stuff is pre-wired and ready to go for regular usage in Linux containers in comparison, I think.

The journey continues.

#FreeBSD #jails #docker #podman #RunBSD

RE: https://mastodon.social/@hyphatech/116296976647581153

Back to FreeBSD: Part 2 — Jails

Via <https://www.reddit.com/r/freebsd/comments/1s4gk0m/back_to_freebsd_part_2_jails/>

＂This time we compare an LXC container and a FreeBSD jail side by side — same goal but different approaches.

Very much opinionated post about jail managers and the ongoing trend to mimic Docker look and feel.＂

#FreeBSD #jail #jails

⚡️ Part 1 clearly struck a nerve. Part 2 is out! https://hypha.pub/back-to-freebsd-part-2

#FreeBSD #jails #containers #lxc

Most of our work consists of sending books to individuals who are incarcerated, choosing books of personal interest to the individual. There are other programs that instead focus on stocking #jail and prison libraries (which can be as small as a single bookcase or book cart). One of those programs, Pages of Redemption in #Washington state, just made the news for delivering 2,000 books to #jails in Benton, Franklin, Walla Walla and Yakima counties:

https://www.nbcrightnow.com/news/washington-man-delivers-thousands-of-books-to-jails-across-southeast-washington/article_abb6edc5-b0fd-4395-85dd-6147685cc1bd.html

#WashingtonState

Running a FreeBSD server with two independent uplinks?

My latest deep dive covers how to mix a physical provider and a BGP tunnel to serve NAT'd, routed, and pure public jail traffic on a single bridge.

We break down Dual-FIB policy routing and show you how to use PF's rtable and reply-to directives to fix asymmetric routing and keep traffic strictly separated.

Policy routing done right: https://blog.hofstede.it/dual-fib-policy-routing-on-freebsd-two-upstreams-one-server-zero-confusion/

#FreeBSD #BGP #Jails #SysAdmin #networking #routing

Great #video by @garyhtech on why #BSD will never own the cloud.

#Linux owns the #cloud and frankly I'm fine with that. #FreeBSD doesn't need to compete with Linux in this area. It may not have the massive ecosystem, but given its strengths, it functions just fine for back end #infrastructure, in general and niche use cases.

People frequently tout FreeBSD for #ZFS and #Jails but honestly I think #Ports and #Poudriere are huge selling points

https://www.youtube.com/watch?v=XWf1z1ifjOc