[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic-devel] The atomic command and setting hostname for containers
- From: Jan Pazdziora <jpazdziora redhat com>
- To: Daniel J Walsh <dwalsh redhat com>
- Cc: atomic-devel projectatomic io
- Subject: Re: [atomic-devel] The atomic command and setting hostname for containers
- Date: Thu, 18 Aug 2016 15:39:39 +0200
On Wed, Aug 17, 2016 at 10:15:18AM -0400, Daniel J Walsh wrote:
> On 08/17/2016 04:00 AM, Jan Pazdziora wrote:
> > in place of some option in LABEL RUN.
> >
> > So during atomic install, I could populate
> > $HOST/var/lib/${NAME}/docker-run-opts with things like
> >
> > -h ipa.example.test
> >
> > or
> >
> > --net host
> >
> > and I could say
> >
> > LABEL RUN_OPTS_FILE /var/lib/${NAME}/docker-run-opts
> > LABEL RUN 'docker run ${RUN_OPTS} ...'
> >
> > in the Dockerfile and the RUN-command would get parameters prepared
> > and persistently stored by the INSTALL-command.
> >
> > Is that something that the team would be willing to consider?
> >
> Sure I would consider this. Please open a PULL Request. We would
Filed as
https://github.com/projectatomic/atomic/pull/541
> probably want to add one for INSTALL, UNINSTALL, RUN ...
The pull request does it for RUN only at this moment, to get initial
feedback about the approach. I can extend it to INSTALL and UNINSTALL
later, or do that in subsequent pull request.
--
Jan Pazdziora
Senior Principal Software Engineer, Identity Management Engineering, Red Hat
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]