From owner-freebsd-questions@FreeBSD.ORG Wed Jun 10 14:52:54 2015 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 2645EAA for ; Wed, 10 Jun 2015 14:52:54 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from mx02.qsc.de (mx02.qsc.de [213.148.130.14]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id DBFAE1C1E for ; Wed, 10 Jun 2015 14:52:53 +0000 (UTC) (envelope-from freebsd@edvax.de) Received: from r56.edvax.de (port-92-195-111-193.dynamic.qsc.de [92.195.111.193]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by mx02.qsc.de (Postfix) with ESMTPS id 5BAB327812; Wed, 10 Jun 2015 16:52:45 +0200 (CEST) Received: from r56.edvax.de (localhost [127.0.0.1]) by r56.edvax.de (8.14.5/8.14.5) with SMTP id t5AEqiK8002402; Wed, 10 Jun 2015 16:52:44 +0200 (CEST) (envelope-from freebsd@edvax.de) Date: Wed, 10 Jun 2015 16:52:44 +0200 From: Polytropon To: Jason Cox Cc: opendaddy@hushmail.com, FreeBSD Mailing List Subject: Re: FreeBSD and Docker Message-Id: <20150610165244.0c6f2ed7.freebsd@edvax.de> In-Reply-To: References: <20150610111135.C81EE2319B@smtp.hushmail.com> Reply-To: Polytropon Organization: EDVAX X-Mailer: Sylpheed 3.1.1 (GTK+ 2.24.5; i386-portbld-freebsd8.2) Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.20 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 10 Jun 2015 14:52:54 -0000 On Wed, 10 Jun 2015 07:29:09 -0700, Jason Cox wrote: > What are you doing wrong? You are trying to run docker on FreeBSD. Docker > is a containerization technology built for Linux. It uses LXC (which is > Linux Containers) for older Kernels or docker specific bits which are now > part of the modern Linux kernel 3.10+. It requires too many Linuxisms which aren't part of FreeBSD's Linux ABI, so expecting Docker to work on FreeBSD is somehow wrong. > Docker is basically FreeBSD Jails, > with a few more features and a lot more security issues. It's surely possible to run a "jail equivalent" of the Docker application package in question (here: Discourse). > I have not looked into Discourse, but any application that requires Docker > is not worth using at this point. Discourse is not exactly _requiring_ Docker - there has been a prepackaged Docker "instance" of all the components you need to run Discourse, not more, not less. It should be possible to run Discourse the "traditional" way - using native FreeBSD technology. > If > you just cannot get Discourse working on FreeBSD, then by all means switch > to a Linux install instead. Make sure it is not centos as it will not have > the update Kernel drivers for better Docker support. That is the final advice. :-) Docker is for Linux, Jails is for FreeBSD. It's somewhat comparable to a "pre-packaged VM image", more or less (probably less). Oh, and doing things like # wget http://getsomething.example.com | sudo bash is definitely _not_ the way you want to install software on FreeBSD. It rather seems to be a new Linuxism that has emerged during the recent years. :-) -- Polytropon Magdeburg, Germany Happy FreeBSD user since 4.0 Andra moi ennepe, Mousa, ...