Re: The status of docker

On 02/02/2019 13:14, Mark Blackman wrote: On 2 Feb 2019, at 11:59, Grzegorz Junka > wrote: On 01/02/2019 22:04, Goran Mekić wrote: On 1 February 2019 20:39:31 CET, Grzegorz Junka wrote: On 31/01/2019 07:50, Mark Blackman wrote: What problem are you trying

Re: The status of docker

> On 2 Feb 2019, at 11:59, Grzegorz Junka wrote: > > > > On 01/02/2019 22:04, Goran Mekić wrote: >> On 1 February 2019 20:39:31 CET, Grzegorz Junka >> wrote: >> On 31/01/2019 07:50, Mark Blackman wrote: >> What problem are you trying to solve with docker? >> >> The

Re: The status of docker

On 01/02/2019 22:04, Goran Mekić wrote: On 1 February 2019 20:39:31 CET, Grzegorz Junka wrote: On 31/01/2019 07:50, Mark Blackman wrote: What problem are you trying to solve with docker? There is a misunderstanding. I am not trying to solve any problem. The team I am w

Re: The status of docker

On 1 February 2019 20:39:31 CET, Grzegorz Junka wrote: >On 31/01/2019 07:50, Mark Blackman wrote: >> What problem are you trying to solve with docker? > >There is a misunderstanding. I am not trying to solve any problem. The >team I am working with is using docker during development (by using a

Re: The status of docker

On 01/02/2019 20:07, Mark Blackman wrote: On 1 Feb 2019, at 19:39, Grzegorz Junka wrote: On 31/01/2019 07:50, Mark Blackman wrote: What problem are you trying to solve with docker? There is a misunderstanding. I am not trying to solve any problem. The team I am working with is using docker

Re: The status of docker

On 2/1/19 1:12 PM, Pete Wright wrote: On 2/1/19 1:07 PM, Grzegorz Junka wrote: On 01/02/2019 19:49, Pete Wright wrote: On 2/1/19 11:39 AM, Grzegorz Junka wrote: On 31/01/2019 07:50, Mark Blackman wrote: What problem are you trying to solve with docker? There is a misunderstanding. I

Re: The status of docker

On 2/1/19 1:07 PM, Grzegorz Junka wrote: On 01/02/2019 19:49, Pete Wright wrote: On 2/1/19 11:39 AM, Grzegorz Junka wrote: On 31/01/2019 07:50, Mark Blackman wrote: What problem are you trying to solve with docker? There is a misunderstanding. I am not trying to solve any problem. The

Re: The status of docker

On 01/02/2019 19:49, Pete Wright wrote: On 2/1/19 11:39 AM, Grzegorz Junka wrote: On 31/01/2019 07:50, Mark Blackman wrote: What problem are you trying to solve with docker? There is a misunderstanding. I am not trying to solve any problem. The team I am working with is using docker durin

Re: The status of docker

> On 1 Feb 2019, at 19:39, Grzegorz Junka wrote: > >> On 31/01/2019 07:50, Mark Blackman wrote: >> What problem are you trying to solve with docker? > > There is a misunderstanding. I am not trying to solve any problem. The team I > am working with is using docker during development (by using

Re: The status of docker

On 2/1/19 11:39 AM, Grzegorz Junka wrote: On 31/01/2019 07:50, Mark Blackman wrote: What problem are you trying to solve with docker? There is a misunderstanding. I am not trying to solve any problem. The team I am working with is using docker during development (by using a preconfigured c

Re: The status of docker

On 31/01/2019 07:50, Mark Blackman wrote: What problem are you trying to solve with docker? There is a misunderstanding. I am not trying to solve any problem. The team I am working with is using docker during development (by using a preconfigured container they avoid having to setup a complex

Re: The status of docker

What problem are you trying to solve with docker? > On 30 Jan 2019, at 20:36, Grzegorz Junka wrote: > >> On 27/01/2019 13:59, Stefan Bethke wrote: >>> Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : >>> Hello, does anyone know the current status of docker on FreeBSD? Wiki >>> https://wiki.fre

Re: The status of docker

On Wed, 30 Jan 2019, Grzegorz Junka wrote: > There is nothing docker-like in FreeBSD. Sure, we have jails and bhyve but > they are faaar from the convenience and support of docker containers that you > can pull directly from docker hub and have a complete application running in a > few lines of co

Re: The status of docker

I would imagine you would just take the docker architectural principles and write some relatively straightforward code to reimplement them with jails > On 30 Jan 2019, at 20:36, Grzegorz Junka wrote: > >> On 27/01/2019 13:59, Stefan Bethke wrote: >>> Am 19.01.2019 um 15:24 schrieb Grzegorz Jun

Re: The status of docker

On 27/01/2019 13:59, Stefan Bethke wrote: Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : Hello, does anyone know the current status of docker on FreeBSD? Wiki https://wiki.freebsd.org/Docker states it's experimental. The last commit in https://github.com/kvasdopil/docker/tree/freebsd-compat i

Re: The status of docker

On Wed, 30 Jan 2019 at 04:57, Paul Kraus wrote: > On Jan 28, 2019, at 2:40 AM, Patrick M. Hausen wrote: > > > > Good morning, > > > >> Am 28.01.2019 um 03:53 schrieb Paul Kraus : > >> (Open)Solaris already had Linux Brand zones, which I’m sure helped get > there much faster. > >> They could alre

Re: The status of docker

On Jan 28, 2019, at 2:40 AM, Patrick M. Hausen wrote: > > Good morning, > >> Am 28.01.2019 um 03:53 schrieb Paul Kraus : >> (Open)Solaris already had Linux Brand zones, which I’m sure helped get there >> much faster. >> They could already run Linux (user space) in a Zone. > > Yes, but how did

Re: The status of docker

Good morning, > Am 28.01.2019 um 03:53 schrieb Paul Kraus : > (Open)Solaris already had Linux Brand zones, which I’m sure helped get there > much faster. > They could already run Linux (user space) in a Zone. Yes, but how did they get there? Is there some technical reason why Linux branded zone

Re: The status of docker

On Jan 22, 2019, at 3:01 PM, Patrick M. Hausen wrote: > > Hi all, > >> Am 22.01.2019 um 20:48 schrieb Grzegorz Junka : >> 2. A docker container in a jail with no native linux kernel, docker is >> running completely in FreeBSD environment >> >> 2 would be most convenient but also most difficult

Re: The status of docker

Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : > > Hello, does anyone know the current status of docker on FreeBSD? Wiki > https://wiki.freebsd.org/Docker states it's experimental. The last commit in > https://github.com/kvasdopil/docker/tree/freebsd-compat is also from 2015. > > There in fact

Re: The status of docker

It’s bad etiquette to post to more than two lists, let’s take this to freebsd-virtualization@. > Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : > > Hello, does anyone know the current status of docker on FreeBSD? Wiki > https://wiki.freebsd.org/Docker states it's experimental. The last commit

Re: The status of docker

On 24/01/2019 13:41, Kamil Kieliszczyk wrote: My 2c on running Docker on FreeBSD: 1) I’m using Docker and Kubernetes quite extensively during my work days so I tried to run Docker on FreeBSD in my free time because.. why not? First I tried to run boot2docker project in VirtualBox as I remembe

Re: The status of docker

My 2c on running Docker on FreeBSD: 1) I’m using Docker and Kubernetes quite extensively during my work days so I tried to run Docker on FreeBSD in my free time because.. why not? First I tried to run boot2docker project in VirtualBox as I remember that it was the way to run Docker on OSX a long

Re: The status of docker

On 23/01/2019 03:21, ss griffon wrote: I'm a bit late to the game, but I wanted to add my 2 cents.  I don't see the benefit of implementing "docker" in FreeBSD.  If you are just implementing the linux system calls i.e. using the linuxulator, then you lose any benefits of running on FreeBSD.  I

Re: The status of docker

> On Jan 22, 2019, at 11:54 PM, Sergey Zakharchenko > wrote: > > Hello there guys, > >> Not quite. I took over the docker freebsd port. Currently I am trying to >> change him to moby project on GH. > > Jochen, I wish you the best of luck. As a couple of cents, and on > behalf of Digital Logger

Re: The status of docker

> On Jan 23, 2019, at 11:26 AM, John Nielsen wrote: > >> On Jan 22, 2019, at 11:54 PM, Sergey Zakharchenko >> wrote: >> >> Hello there guys, >> >>> Not quite. I took over the docker freebsd port. Currently I am trying to >>> change him to moby project on GH. >> >> Jochen, I wish you the b

Re: The status of docker

Hello there guys, > Not quite. I took over the docker freebsd port. Currently I am trying to > change him to moby project on GH. Jochen, I wish you the best of luck. As a couple of cents, and on behalf of Digital Loggers, Inc., I've uploaded some old patches that we use to run an ancient version

Re: The status of docker

Am 22.01.19 um 20:48 schrieb Grzegorz Junka: > On 22/01/2019 08:28, Patrick M. Hausen wrote: >> Good morning, >> >>> Am 22.01.2019 um 03:57 schrieb Craig Rodrigues : >>> I hope I am wrong, but unfortunately I think getting Docker to work on >>> natively on FreeBSD is ultimately a losing battle, >>

Re: The status of docker

I'm a bit late to the game, but I wanted to add my 2 cents. I don't see the benefit of implementing "docker" in FreeBSD. If you are just implementing the linux system calls i.e. using the linuxulator, then you lose any benefits of running on FreeBSD. It seems like implementing the docker interfa

Re: The status of docker

Hi! > Am 22.01.2019 um 21:09 schrieb Grzegorz Junka : > BTW is Joyent is any way related to Oracle? Why would they want to support > zones? Is the support they implemented open sourced? Sorry, I don’t know many details. Their cloud is built on Open Solaris, hence the connection. IIRC the company

Re: The status of docker

> On 22/01/2019 20:01, Patrick M. Hausen wrote: > > Hi all, > > > >> Am 22.01.2019 um 20:48 schrieb Grzegorz Junka >> >: > >> 2. A docker container in a jail with no native linux kernel, docker > >> is running completely in FreeBSD environment > >> > >> 2 would be most co

Re: The status of docker

On 22/01/2019 20:01, Patrick M. Hausen wrote: Hi all, Am 22.01.2019 um 20:48 schrieb Grzegorz Junka >: 2. A docker container in a jail with no native linux kernel, docker is running completely in FreeBSD environment 2 would be most convenient but also most difficult a

Re: The status of docker

Hi all, > Am 22.01.2019 um 20:48 schrieb Grzegorz Junka : > 2. A docker container in a jail with no native linux kernel, docker is > running completely in FreeBSD environment > > 2 would be most convenient but also most difficult as all smallest docker > features would need to be ported nativel

Re: The status of docker

On 22/01/2019 08:28, Patrick M. Hausen wrote: Good morning, Am 22.01.2019 um 03:57 schrieb Craig Rodrigues : I hope I am wrong, but unfortunately I think getting Docker to work on natively on FreeBSD is ultimately a losing battle, unless you can get a team of several developers to work on it fu

Re: The status of docker

Good morning, > Am 22.01.2019 um 03:57 schrieb Craig Rodrigues : > I hope I am wrong, but unfortunately I think getting Docker to work on > natively on FreeBSD is ultimately a losing battle, > unless you can get a team of several developers to work on it full time. I have the same gut feeling, bu

Re: The status of docker

On Mon, Jan 21, 2019 at 4:50 AM Jochen Neumeister wrote: > > Not quite. I took over the docker freebsd port. Currently I am trying to > change him to moby project on GH. > > Also, I'll take a closer look at Kubernetes for FreeBSD in the near future. > > > Jochen, Thank you for taking on the Dock

Re: The status of docker

On 21/01/2019 12:48, Jochen Neumeister wrote: On 19.01.19 16:31, Rainer Duffner wrote: Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : Has this project been completed and now only needs testing, or has it been abandoned, or maybe the approach has changed and I am looking in a wrong place?

Re: The status of docker

On 19.01.19 16:31, Rainer Duffner wrote: Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : Has this project been completed and now only needs testing, or has it been abandoned, or maybe the approach has changed and I am looking in a wrong place? AFAIK, it’s dead. Docker is a Linux-thing.

Re: The status of docker

> Am 20.01.2019 um 11:53 schrieb Grzegorz Junka : > > I did use bhyve with CentOS in another project but that approach wouldn't > quite work in this situation as for my understanding, unless you propose that > I run docker on a Linux distribution running in bhyve? Yes, that would be the out

Re: The status of docker

On 19/01/2019 21:56, Frank Leonhardt wrote: On 19 January 2019 15:31:11 GMT, Rainer Duffner wrote: Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : Has this project been completed and now only needs testing, or has it been abandoned, or maybe the approach has changed and I am looking in a wr

Re: The status of docker

On 19 January 2019 15:31:11 GMT, Rainer Duffner wrote: > > >> Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : >> >> Has this project been completed and now only needs testing, or has it >been abandoned, or maybe the approach has changed and I am looking in a >wrong place? > > > > >AFAIK, it’s d

Re: The status of docker

> Am 19.01.2019 um 15:24 schrieb Grzegorz Junka : > > Has this project been completed and now only needs testing, or has it been > abandoned, or maybe the approach has changed and I am looking in a wrong > place? AFAIK, it’s dead. Docker is a Linux-thing. Your best bet is to run Linux in

The status of docker

Hello, does anyone know the current status of docker on FreeBSD? Wiki https://wiki.freebsd.org/Docker states it's experimental. The last commit in https://github.com/kvasdopil/docker/tree/freebsd-compat is also from 2015. There in fact are two ports, freebsd-docker (from 2015) and docker (18.