Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Docker on FreeBSD

wiki.freebsd.org

Post reply on HN
Print view View original

11–20 of 69 posts

Re: Docker on FreeBSD

#11

Post by sydney6 »

gonzo wrote: post #6
ObviousScience wrote: post #3

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.

http://youtu.be/OXS8ljif9b8

Edit: First 5 Minutes De Raadt speaks about Mitigation Techniques in comparison to other OSs, including FBSD. I fear, this is still true in mid-2015..

Re: Docker on FreeBSD

#12

Post by icebraining »

lifeisstillgood wrote: post #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! :-)

Docker is a management tool for the underlying jail-like features implemented by the kernel (cgroups, mainly). There's no reason why it can't be used to manage *BSD jails, ie., create jails from Dockerfiles, download jail templates from a public repository, etc.

Re: Docker on FreeBSD

#13

Post by feld »

sydney6 wrote: post #11
gonzo wrote: post #6

Earlier quoted context omitted.

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

http://youtu.be/OXS8ljif9b8 Edit: First 5 Minutes De Raadt speaks about Mitigation Techniques in comparison to other OSs, including FBSD. I fear, this is still true in mid-2015..

It's like nobody has ever heard of Capsicum

Re: Docker on FreeBSD

#14

Post by tedunangst »

gonzo wrote: post #6
ObviousScience wrote: post #3

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.

Removal of gets() from libc.

Re: Docker on FreeBSD

#15

Post by sydney6 »

feld wrote: post #13
sydney6 wrote: post #11

Earlier quoted context omitted.

http://youtu.be/OXS8ljif9b8 Edit: First 5 Minutes De Raadt speaks about Mitigation Techniques in comparison to other OSs, including FBSD. I fear, this is still true in mid-2015..

It's like nobody has ever heard of Capsicum

I believe capsicum is/will be used for sandboxing sshd, ping and tcpdump. Furthermore i know about Security Appliances making use of it, but that's about it, to be honest.

Re: Docker on FreeBSD

#16

Post by kev009 »

noinsight wrote: post #4
ObviousScience wrote: post #3

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…

Virtualbox - sounds like some kind of ports problem, maybe GTK vs Qt? Works for me on PC-BSD and FreeBSD -CURRENT under KDE.

Suspend/resume should be working pretty well in -CURRENT, unfortunately 11.0 is still a ways out if you want a -RELEASE.

Re: Docker on FreeBSD

#17

Post by terhechte »

vezzy-fnord wrote: post #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 jus…

Do you happen to have a link to the XPC port? I just did a cursory search but couldn't find anything.

Re: Docker on FreeBSD

#18

Post by swills »

noinsight wrote: post #4
ObviousScience wrote: post #3

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…

The Chromium issue was fixed recently. Try updating your Chromium to at least 43.0.2357.132.

The VirtualBox issue is long standing, it's caused by the fact that vbox is setuid. Try this:

env KDE_FORK_SLAVES=1 VirtualBox

Re: Docker on FreeBSD

#19

Post by vezzy-fnord »

terhechte wrote: post #17
vezzy-fnord wrote: post #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 jus…

Do you happen to have a link to the XPC port? I just did a cursory search but couldn't find anything.

It's in Kip Macy's work branch: https://github.com/kmacy/NextBSD

/lib/lib[asl, dispatch, launch, mach, osxsupport, xpc].

The XPC stuff is mostly Jakub Klama's work, I think.

Re: Docker on FreeBSD

#20

Post by swills »

noinsight wrote: post #4
ObviousScience wrote: post #3

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…

Oh and about the X thing, do you have a Haswell processor? And are you using the VGA driver for X? I had that, bought a $20 ATI card, works fine now, 3D acceleration in KWM and everything.
Post reply on HN