Live data from Hacker News

Docker on FreeBSD

wiki.freebsd.org

1–10 of 69 posts

Re: Docker on FreeBSD

#2
The FreeBSD people seem to be on a roll when it comes to porting things. They mention a 64-bit Linux compatibility layer they recently rolled out in this post. But in addition, some iXsystems employees have ported much of the OSF Mach kernel (sans memory object/external pager interface) as a module, plus partial or full implementations of XPC, libdispatch, ASL (Apple System Logger), liblaunch and other facilities just so they can run the low-level Darwin/OS X userspace and launchd, especially. FreeNAS then wrote Cython bindings to all this for use in their system services. This is all in feature branches atm, but it should be rolling out soon enough.

It's insane.

Re: Docker on FreeBSD

#3

The FreeBSD people seem to be on a roll when it comes to porting things. They mention a 64-bit Linux compatibility layer they recently rolled out in this post. But in addition, some iXsystems employees have ported much of the OSF Mach kernel (sans memory object/external pager interface) as a module, plus partial or full implementations of XPC, libdispatch, ASL (Apple System Logger), liblaunch and other facilities jus…

To be honest, I think OpenBSD is ahead on some fronts (research on security mechanisms, for instance), but the reason that I tend to use FreeBSD is that it actually works with software packages.

So the computers are based on FreeBSD (which manages the hypervisor -- and soon container daemon!), and appliances only are based on OpenBSD.

Compatibility ftw.

Re: Docker on FreeBSD

#4

The FreeBSD people seem to be on a roll when it comes to porting things. They mention a 64-bit Linux compatibility layer they recently rolled out in this post. But in addition, some iXsystems employees have ported much of the OSF Mach kernel (sans memory object/external pager interface) as a module, plus partial or full implementations of XPC, libdispatch, ASL (Apple System Logger), liblaunch and other facilities jus…

To be honest, I think OpenBSD is ahead on some fronts (research on security mechanisms, for instance), but the reason that I tend to use FreeBSD is that it actually works with software packages. So the computers are based on FreeBSD (which manages the hypervisor -- and soon container daemon!), and appliances only are based on OpenBSD. Compatibility ftw.

> it actually works with software packages.

Well I don't know about that. I can't open Settings in Chromium at all anymore, the whole browser crashes. It also constantly uses 100% CPU for something so with Chromium open my load is always >1.

In VirtualBox none of the file open dialogs work.

If I switch to a console from X the whole screen glitches and gets stuck, I have to SSH in to restart/stop X.

Suspend doesn't work for me.

So yeah, it doesn't work on the desktop as well as Linux does. Haven't had any problems with it as a server though.

Re: Docker on FreeBSD

#5

The FreeBSD people seem to be on a roll when it comes to porting things. They mention a 64-bit Linux compatibility layer they recently rolled out in this post. But in addition, some iXsystems employees have ported much of the OSF Mach kernel (sans memory object/external pager interface) as a module, plus partial or full implementations of XPC, libdispatch, ASL (Apple System Logger), liblaunch and other facilities jus…

To be honest, I think OpenBSD is ahead on some fronts (research on security mechanisms, for instance), but the reason that I tend to use FreeBSD is that it actually works with software packages. So the computers are based on FreeBSD (which manages the hypervisor -- and soon container daemon!), and appliances only are based on OpenBSD. Compatibility ftw.

I use OpenBSD and haven't found software to be an issue. Certainly mainstream stuff such as Chromium, Firefox, LibreOffice, VLC, Evince, Gimp, Inkscape... all works.

Re: Docker on FreeBSD

#6

The FreeBSD people seem to be on a roll when it comes to porting things. They mention a 64-bit Linux compatibility layer they recently rolled out in this post. But in addition, some iXsystems employees have ported much of the OSF Mach kernel (sans memory object/external pager interface) as a module, plus partial or full implementations of XPC, libdispatch, ASL (Apple System Logger), liblaunch and other facilities jus…

To be honest, I think OpenBSD is ahead on some fronts (research on security mechanisms, for instance), but the reason that I tend to use FreeBSD is that it actually works with software packages. So the computers are based on FreeBSD (which manages the hypervisor -- and soon container daemon!), and appliances only are based on OpenBSD. Compatibility ftw.

> research on security mechanisms, for instance)

Citation(s) requested.

Re: Docker on FreeBSD

#8

Earlier quoted context omitted.

To be honest, I think OpenBSD is ahead on some fronts (research on security mechanisms, for instance), but the reason that I tend to use FreeBSD is that it actually works with software packages. So the computers are based on FreeBSD (which manages the hypervisor -- and soon container daemon!), and appliances only are based on OpenBSD. Compatibility ftw.

> it actually works with software packages. Well I don't know about that. I can't open Settings in Chromium at all anymore, the whole browser crashes. It also constantly uses 100% CPU for something so with Chromium open my load is always >1. In VirtualBox none of the file open dialogs work. If I switch to a console from X the whole screen glitches and gets stuck, I have to SSH in to restart/stop X. Suspend doesn't wo…

There is a bug in the kernel that returns the wrong error message when Chrome/Chromium attempts to get a variable. This will be fixed in 10.2.

See: https://twitter.com/cperciva/status/619969753566744576

Re: Docker on FreeBSD

#9
post #6

Earlier quoted context omitted.

To be honest, I think OpenBSD is ahead on some fronts (research on security mechanisms, for instance), but the reason that I tend to use FreeBSD is that it actually works with software packages. So the computers are based on FreeBSD (which manages the hypervisor -- and soon container daemon!), and appliances only are based on OpenBSD. Compatibility ftw.

> research on security mechanisms, for instance) Citation(s) requested.

https://en.m.wikipedia.org/wiki/Comparison_of_BSD_operating_...

Re: Docker on FreeBSD

#10
I just assumed we would not do docker because we have had jails for so long. In fact, ZFS and jail is docker no? I admit no familiarity with docker (played with LXC years ago and thought - gosh it's like jail! :-)
Post reply on HN