such
systems?
Thanks,
Kevin
From: Lars Kellogg-Stedman [l...@redhat.com]
Sent: Thursday, October 16, 2014 7:14 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] on Dockerfile patterns
On Fri, Oct 17, 2014 at 12:44:50PM +1100, Angus Lees
nt Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] on Dockerfile patterns
On Fri, Oct 17, 2014 at 12:44:50PM +1100, Angus Lees wrote:
> You just need to find the pid of a process in the container (perhaps using
> docker inspect to go from container name -> pid) and
On Thu, 16 Oct 2014, Lars Kellogg-Stedman wrote:
On Fri, Oct 17, 2014 at 12:44:50PM +1100, Angus Lees wrote:
You just need to find the pid of a process in the container (perhaps using
docker inspect to go from container name -> pid) and then:
nsenter -t $pid -m -u -i -n -p -w
Note also that
On Fri, Oct 17, 2014 at 12:44:50PM +1100, Angus Lees wrote:
> You just need to find the pid of a process in the container (perhaps using
> docker inspect to go from container name -> pid) and then:
> nsenter -t $pid -m -u -i -n -p -w
Note also that the 1.3 release of Docker ("any day now") will
On Wed, 15 Oct 2014 08:19:03 PM Clint Byrum wrote:
> > > I think it would be a good idea for containers' filesystem contents to
> > > be a whole distro. What's at question in this thread is what should be
> > > running. If we can just chroot into the container's FS and run
> > > apt-get/yum
> > > i
Excerpts from Angus Lees's message of 2014-10-15 17:30:52 -0700:
> On Wed, 15 Oct 2014 09:51:03 AM Clint Byrum wrote:
> > Excerpts from Vishvananda Ishaya's message of 2014-10-15 07:52:34 -0700:
> > > On Oct 14, 2014, at 1:12 PM, Clint Byrum wrote:
> > > > Excerpts from Lars Kellogg-Stedman's mess
On Wed, 15 Oct 2014 12:40:16 AM Fox, Kevin M wrote:
> Systemd has invested a lot of time/effort to be able to relaunch failed
> services, support spawning and maintaining unix sockets and services across
> them, etc, that you'd have to push out of and across docker containers. All
> of that can be
On Wed, 15 Oct 2014 09:02:03 PM Jay Pipes wrote:
> On 10/15/2014 08:30 PM, Angus Lees wrote:
> > On Wed, 15 Oct 2014 09:51:03 AM Clint Byrum wrote:
> >> Excerpts from Vishvananda Ishaya's message of 2014-10-15 07:52:34 -0700:
> >>> On Oct 14, 2014, at 1:12 PM, Clint Byrum wrote:
> Excerpts fr
On 10/15/2014 08:30 PM, Angus Lees wrote:
On Wed, 15 Oct 2014 09:51:03 AM Clint Byrum wrote:
Excerpts from Vishvananda Ishaya's message of 2014-10-15 07:52:34 -0700:
On Oct 14, 2014, at 1:12 PM, Clint Byrum wrote:
Excerpts from Lars Kellogg-Stedman's message of 2014-10-14 12:50:48
-0700:
On
On Wed, 15 Oct 2014 09:51:03 AM Clint Byrum wrote:
> Excerpts from Vishvananda Ishaya's message of 2014-10-15 07:52:34 -0700:
> > On Oct 14, 2014, at 1:12 PM, Clint Byrum wrote:
> > > Excerpts from Lars Kellogg-Stedman's message of 2014-10-14 12:50:48
-0700:
> > >> On Tue, Oct 14, 2014 at 03:25:5
On Wed, 2014-10-15 at 11:24 -0400, David Vossel wrote:
>
> - Original Message -
> > On Tue, 2014-10-14 at 19:52 -0400, David Vossel wrote:
> > >
> > > - Original Message -
> > > > Ok, why are you so down on running systemd in a container?
> > >
> > > It goes against the grain.
>
On 10/14/2014 06:10 PM, Clint Byrum wrote:
Excerpts from Fox, Kevin M's message of 2014-10-14 17:40:16 -0700:
I'm not arguing that everything should be managed by one systemd, I'm
just saying, for certain types of containers, a single docker container
with systemd in it might be preferable to tr
On 10/14/2014 05:44 PM, Angus Lees wrote:
On Tue, 14 Oct 2014 07:51:54 AM Steven Dake wrote:
Angus,
On 10/13/2014 08:51 PM, Angus Lees wrote:
I've been reading a bunch of the existing Dockerfiles, and I have two
humble requests:
1. It would be good if the "interesting" code came from python
lopment Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] on Dockerfile patterns
- Original Message -
Same thing works with cloud init too...
I've been waiting on systemd working inside a container for a while. it
seems
to work now.
oh no...
The idea b
On Wed, Oct 15, 2014 at 01:50:08PM -0400, David Vossel wrote:
> Something like LSB init scripts except tailored towards the container use
> case.
> The primary difference would be that the 'start' action of this new standard
> wouldn't fork. Instead 'start' would be pid 1. The 'status' could be ch
- Original Message -
> Excerpts from Vishvananda Ishaya's message of 2014-10-15 07:52:34 -0700:
> >
> > On Oct 14, 2014, at 1:12 PM, Clint Byrum wrote:
> >
> > > Excerpts from Lars Kellogg-Stedman's message of 2014-10-14 12:50:48
> > > -0700:
> > >> On Tue, Oct 14, 2014 at 03:25:56PM -
Excerpts from Vishvananda Ishaya's message of 2014-10-15 07:52:34 -0700:
>
> On Oct 14, 2014, at 1:12 PM, Clint Byrum wrote:
>
> > Excerpts from Lars Kellogg-Stedman's message of 2014-10-14 12:50:48 -0700:
> >> On Tue, Oct 14, 2014 at 03:25:56PM -0400, Jay Pipes wrote:
> >>> I think the above st
On Wed, Oct 15, 2014 at 07:52:56AM -0700, Vishvananda Ishaya wrote:
> There must be a standard way
> to do this stuff or people will continue to build fat containers with
> all of their pet tools inside. This means containers will just be
> another incarnation of virtualization.
I wouldn't spend t
- Original Message -
> On Tue, 2014-10-14 at 19:52 -0400, David Vossel wrote:
> >
> > - Original Message -
> > > Ok, why are you so down on running systemd in a container?
> >
> > It goes against the grain.
> >
> > From a distributed systems view, we gain quite a bit of control
s is going on. Its A way to know things are
> bad, but you can't necessarily rely on it to know the container's healty.
> You need more robust checks for that.
>
> Thanks,
> Kevin
>
> ____________________
> From: David Vossel [dvos...@redhat.com]
> Sent:
On Oct 14, 2014, at 1:12 PM, Clint Byrum wrote:
> Excerpts from Lars Kellogg-Stedman's message of 2014-10-14 12:50:48 -0700:
>> On Tue, Oct 14, 2014 at 03:25:56PM -0400, Jay Pipes wrote:
>>> I think the above strategy is spot on. Unfortunately, that's not how the
>>> Docker ecosystem works.
>>
On Oct 14, 2014, at 1:21 PM, Lars Kellogg-Stedman wrote:
> On Tue, Oct 14, 2014 at 04:06:22PM -0400, Jay Pipes wrote:
>> I understand that general feeling, but system administration tasks like
>> debugging networking issues or determining and grepping log file locations
>> or diagnosing packagin
On 10/14/2014 01:12 PM, Clint Byrum wrote:
Excerpts from Lars Kellogg-Stedman's message of 2014-10-14 12:50:48 -0700:
On Tue, Oct 14, 2014 at 03:25:56PM -0400, Jay Pipes wrote:
I think the above strategy is spot on. Unfortunately, that's not how the
Docker ecosystem works.
I'm not sure I agree
On Tue, 2014-10-14 at 19:52 -0400, David Vossel wrote:
>
> - Original Message -
> > Ok, why are you so down on running systemd in a container?
>
> It goes against the grain.
>
> From a distributed systems view, we gain quite a bit of control by maintaining
> "one service per container".
And here is the best practice for using Dockerfile.
https://docs.docker.com/articles/dockerfile_best-practices/
On Tue, Oct 14, 2014 at 11:51 AM, Angus Lees wrote:
> I've been reading a bunch of the existing Dockerfiles, and I have two
> humble
> requests:
>
>
> 1. It would be good if the "inter
Excerpts from Fox, Kevin M's message of 2014-10-14 17:40:16 -0700:
> I'm not arguing that everything should be managed by one systemd, I'm
> just saying, for certain types of containers, a single docker container
> with systemd in it might be preferable to trying to slice it unnaturally
> into seve
On Tue, 14 Oct 2014 07:51:54 AM Steven Dake wrote:
> Angus,
>
> On 10/13/2014 08:51 PM, Angus Lees wrote:
> > I've been reading a bunch of the existing Dockerfiles, and I have two
> > humble requests:
> >
> >
> > 1. It would be good if the "interesting" code came from python
> > sdist/bdists
> >
Thanks,
Kevin
From: David Vossel [dvos...@redhat.com]
Sent: Tuesday, October 14, 2014 4:52 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] on Dockerfile patterns
- Original Message -
> Ok,
;
> From: David Vossel [dvos...@redhat.com]
> Sent: Tuesday, October 14, 2014 3:14 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [kolla] on Dockerfile patterns
>
> - Original Message -
day, October 14, 2014 3:14 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [kolla] on Dockerfile patterns
>
> - Original Message -
> > Same thing works with cloud init too...
> >
> >
> > I'v
> Sent: Tuesday, October 14, 2014 12:10 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [kolla] on Dockerfile patterns
>
> On Tue, Oct 14, 2014 at 02:45:30PM -0400, Jay Pipes wrote:
> > With Docker, you are limited to the
> Sent: Tuesday, October 14, 2014 12:10 PM
> To: OpenStack Development Mailing List (not for usage questions)
> Subject: Re: [openstack-dev] [kolla] on Dockerfile patterns
>
> On Tue, Oct 14, 2014 at 02:45:30PM -0400, Jay Pipes wrote:
> > With Docker, you are limited to the
Angus Lees wrote:
> I've been reading a bunch of the existing Dockerfiles, and I have two humble
> requests:
>
>
> 1. It would be good if the "interesting" code came from python sdist/bdists
> rather than rpms.
>
> This will make it possible to rebuild the containers using code from a
> priva
On Tue, Oct 14, 2014 at 04:06:22PM -0400, Jay Pipes wrote:
> I understand that general feeling, but system administration tasks like
> debugging networking issues or determining and grepping log file locations
> or diagnosing packaging issues for OpenStack services or performing database
> logfile
Excerpts from Lars Kellogg-Stedman's message of 2014-10-14 12:50:48 -0700:
> On Tue, Oct 14, 2014 at 03:25:56PM -0400, Jay Pipes wrote:
> > I think the above strategy is spot on. Unfortunately, that's not how the
> > Docker ecosystem works.
>
> I'm not sure I agree here, but again nobody is forcin
On 10/14/2014 03:50 PM, Lars Kellogg-Stedman wrote:
On Tue, Oct 14, 2014 at 03:25:56PM -0400, Jay Pipes wrote:
I think the above strategy is spot on. Unfortunately, that's not how the
Docker ecosystem works.
I'm not sure I agree here, but again nobody is forcing you to use this
tool.
I know
On Tue, Oct 14, 2014 at 03:25:56PM -0400, Jay Pipes wrote:
> I think the above strategy is spot on. Unfortunately, that's not how the
> Docker ecosystem works.
I'm not sure I agree here, but again nobody is forcing you to use this
tool.
> operating system that the image is built for. I see you di
assumes you can just systemctl start foo;
Kevin
From: Lars Kellogg-Stedman [l...@redhat.com]
Sent: Tuesday, October 14, 2014 12:10 PM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] on Dockerfile patterns
On Tue, 14 Oct 2014, Jay Pipes wrote:
This means you now have to know the system administrative comments and setup
for two operating systems ... or go find a Fedora20 image for mysql
somewhere.
For sake of conversation and devil's advocacy let me ask, in
response to this paragraph, "why [do y
On 10/14/2014 03:10 PM, Lars Kellogg-Stedman wrote:
On Tue, Oct 14, 2014 at 02:45:30PM -0400, Jay Pipes wrote:
With Docker, you are limited to the operating system of whatever the image
uses.
See, that's the part I disagree with. What I was saying about ansible
and puppet in my email is that
On Tue, Oct 14, 2014 at 02:45:30PM -0400, Jay Pipes wrote:
> With Docker, you are limited to the operating system of whatever the image
> uses.
See, that's the part I disagree with. What I was saying about ansible
and puppet in my email is that I think the right thing to do is take
advantage of t
On 10/14/2014 01:28 PM, Lars Kellogg-Stedman wrote:
On Tue, Oct 14, 2014 at 12:33:42PM -0400, Jay Pipes wrote:
Can I use your Dockerfiles to build Ubuntu/Debian images instead of only
Fedora images?
Not easily, no.
Seems to me that the image-based Docker system makes the
resulting container
On Tue, Oct 14, 2014 at 12:33:42PM -0400, Jay Pipes wrote:
> Can I use your Dockerfiles to build Ubuntu/Debian images instead of only
> Fedora images?
Not easily, no.
> Seems to me that the image-based Docker system makes the
> resulting container quite brittle -- since a) you can't use configura
On 10/14/2014 10:49 AM, Lars Kellogg-Stedman wrote:
On Tue, Oct 14, 2014 at 02:51:15PM +1100, Angus Lees wrote:
1. It would be good if the "interesting" code came from python sdist/bdists
rather than rpms.
I agree in principal, although starting from packages right now lets
us ignore a whole h
the other
clients, and forcing an unplanned upgrade of everything else. :/
From: Chris Dent [chd...@redhat.com]
Sent: Tuesday, October 14, 2014 3:54 AM
To: OpenStack Development Mailing List (not for usage questions)
Subject: Re: [openstack-dev] [kolla] on
Angus,
On 10/13/2014 08:51 PM, Angus Lees wrote:
I've been reading a bunch of the existing Dockerfiles, and I have two humble
requests:
1. It would be good if the "interesting" code came from python sdist/bdists
rather than rpms.
This will make it possible to rebuild the containers using code
On Tue, Oct 14, 2014 at 02:51:15PM +1100, Angus Lees wrote:
> 1. It would be good if the "interesting" code came from python sdist/bdists
> rather than rpms.
I agree in principal, although starting from packages right now lets
us ignore a whole host of issues. Possibly we'll hit that change down
On Tue, 14 Oct 2014, Angus Lees wrote:
2. I think we should separate out "run the server" from "do once-off setup".
Yes! Otherwise it feels like the entire point of using containers
and dockerfiles is rather lost.
--
Chris Dent tw:@anticdent freenode:cdent
https://tank.peermore.com/tanks/cden
I've been reading a bunch of the existing Dockerfiles, and I have two humble
requests:
1. It would be good if the "interesting" code came from python sdist/bdists
rather than rpms.
This will make it possible to rebuild the containers using code from a private
branch or even unsubmitted code,
49 matches
Mail list logo
