Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 28 Jul 2015 21:14:20 -0500
From:      Larry Rosenman <ler@lerctr.org>
To:        Benjamin Perrault <ben.perrault@gmail.com>
Cc:        Michael Dexter <editor@callfortesting.org>, owner-freebsd-virtualization@freebsd.org, freebsd-virtualization@freebsd.org
Subject:   Re: docker info?
Message-ID:  <8d8ac6cf02de937085aa51bfdb90c484@thebighonker.lerctr.org>
In-Reply-To: <8C558056-77D5-46C1-899B-84C8FBF5E63A@gmail.com>
References:  <4d6bdf33235afb887de3c0092073db5a@thebighonker.lerctr.org> <55B7BAC0.2040703@callfortesting.org> <CAKnrJN-JC6OBt7RYFHi-dCuMu-OBaRhgizMN3sm%2BHTiH5gcm9g@mail.gmail.com> <55B82FF6.4040500@callfortesting.org> <abc4a58afccd46e37d3a59b8c15f08ce@thebighonker.lerctr.org> <8C558056-77D5-46C1-899B-84C8FBF5E63A@gmail.com>

next in thread | previous in thread | raw e-mail | index | archive | help
On 2015-07-28 21:10, Benjamin Perrault wrote:
>> On Jul 28, 2015, at 6:55 PM, Larry Rosenman <ler@lerctr.org> wrote:
>> 
>> On 2015-07-28 20:44, Michael Dexter wrote:
>>> On 7/28/15 1:17 PM, Kegan Myers wrote:
>>>> Make sure you have permissions. Docker isn't good at figuring out 
>>>> that you
>>>> need sudo or other permissions to talk to the socket.
>>> Also, do make sure you are using a recent version of 11 CURRENT or a
>>> 10.2 BETA/RC. I do not know what errors will be thrown by older
>>> versions of FreeBSD with Linux images, though they will support
>>> FreeBSD images with some risk of ABI mismatch.
>>> Michael
>>> _______________________________________________
>>> freebsd-virtualization@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-virtualization
>>> To unsubscribe, send any mail to
>>> "freebsd-virtualization-unsubscribe@freebsd.org"
>> 
>> I'm running absolutely top of tree.
>> 
>> borg.lerctr.org /home/ler $ sudo -s
>> Password:
>> borg.lerctr.org /home/ler # docker info
>> Get http:///var/run/docker.sock/v1.19/info: EOF. Are you trying to 
>> connect to a TLS-enabled daemon without TLS?
>> borg.lerctr.org /home/ler # ps auxw|grep docker
>> root        867   0.0  0.0  14412  2220  -  Is   16:48      0:00.00 
>> daemon: /usr/local/bin/docker[868] (daemon)
>> root        868   0.0  0.0  38628 16116  -  S    16:48      0:12.21 
>> /usr/local/bin/docker -d -e jail -s zfs -g /usr/docker -D
>> root       3544   0.0  0.0  18772  2548  0  S+   20:54      0:00.00 
>> grep docker
>> borg.lerctr.org /home/ler # uname -aKU
>> FreeBSD borg.lerctr.org 11.0-CURRENT FreeBSD 11.0-CURRENT #29 r285983: 
>> Tue Jul 28 16:15:05 CDT 2015     
>> root@borg.lerctr.org:/usr/obj/usr/src/sys/VT-LER  amd64 1100077 
>> 1100077
>> borg.lerctr.org /home/ler #
>> 
>> borg.lerctr.org /home/ler # pkg info docker-freebsd
>> docker-freebsd-20150625
>> Name           : docker-freebsd
>> Version        : 20150625
>> Installed on   : Wed Jul 22 11:17:21 CDT 2015
>> Origin         : sysutils/docker-freebsd
>> Architecture   : freebsd:11:x86:64
>> Prefix         : /usr/local
>> Categories     : sysutils
>> Licenses       : APACHE20
>> Maintainer     : kmoore@FreeBSD.org
>> WWW            : https://github.com/kvasdopil/docker
>> Comment        : Docker containment system
>> Annotations    :
>> Flat size      : 11.5MiB
>> Description    :
>> Docker is an open source project to pack, ship and run any
>> application as a lightweight container.
>> 
>> Docker containers are both hardware-agnostic and platform-agnostic.
>> This means they can run anywhere, from your laptop to the largest
>> EC2 compute instance and everything in between - and they don't
>> require you to use a particular language, framework or packaging
>> system. That makes them great building blocks for deploying and
>> scaling web apps, databases, and backend services without depending
>> on a particular stack or provider.
>> 
>> WWW: https://github.com/kvasdopil/docker
>> 
>> borg.lerctr.org /home/ler #
>> —
> 
> ~20% of a few customers containers have had issues - from stability to
> performance to bizarre behavior - but most of it is rather new stuff
> based off CoreOS,  Ubuntu 15.x, Debian 8.1, etc. - with CoreOS showing
> issue the most often. These all have VERY recent kernels, so it’s
> likely missing ABI functionality in the emulation layer.
> 
> With that said - I’ve found that Ubuntu 12/14 LTS and Centos/RHEL 6.x
> containers work great. Most Centos 7 ones we’ve tested also seem to be
> okay - though later 7/7.1 have show high cpu usage and erratic network
> performance. Once I have time, I might delve deeper into it - though
> it’s not a huge priority at the moment.
> 
> Hopefully that was useful in some capacity.
> 
> best,
> -bp
> @creepingfur
> ========================
> You shouldn’t let poets lie to you.
> 	- Bjork
i docker info supposed to work from the HOST OS or in the container?  
I've been trying it from the Host OS.

-- 
Larry Rosenman                     http://www.lerctr.org/~ler
Phone: +1 214-642-9640                 E-Mail: ler@lerctr.org
US Mail: 108 Turvey Cove, Hutto, TX 78634-5688




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?8d8ac6cf02de937085aa51bfdb90c484>