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
> >
On 08/17/2016 04:00 AM, Jan Pazdziora wrote:
> On Wed, Apr 20, 2016 at 02:31:22PM +0200, Jan Pazdziora wrote:
>> On Tue, Apr 19, 2016 at 02:02:51PM -0700, Daniel J Walsh wrote:
>>> But I like your example better. atomic install should almost always be a
>>> privileged container.
>> I think my on
On Wed, Aug 17, 2016 at 10:00:41AM +0200, Jan Pazdziora wrote:
>
> For me, the ideal approach would be adding ability to the atomic
> command to read some location, specified by some LABEL like
> RUN_OPTS_FILE and expose parameters found in file on that location
> in place of some option in LABEL
On Wed, Apr 20, 2016 at 02:31:22PM +0200, Jan Pazdziora wrote:
> On Tue, Apr 19, 2016 at 02:02:51PM -0700, Daniel J Walsh wrote:
> >
> > But I like your example better. atomic install should almost always be a
> > privileged container.
>
> I think my only concern is that RUN will have to be priv
Yes,
https://github.com/kubernetes/kubernetes/tree/master/cluster/addons/dns#a-records-and-hostname-based-on-pod-annotations---a-beta-feature-in-kubernetes-v12
On Wed, Apr 20, 2016 at 11:02 AM, Jan Pazdziora wrote:
> On Wed, Apr 20, 2016 at 10:53:57AM -0400, Clayton Coleman wrote:
>> Kubernetes
On Wed, Apr 20, 2016 at 10:53:57AM -0400, Clayton Coleman wrote:
> Kubernetes injects a specific hostname that corresponds to the DNS
> name assigned by Kube (in some cases).
So what is the workflow when the container has to be run with
hostname ipa.example.com, otherwise all sorts of things in th
Kubernetes injects a specific hostname that corresponds to the DNS
name assigned by Kube (in some cases).
On Wed, Apr 20, 2016 at 10:49 AM, Jan Pazdziora wrote:
> On Wed, Apr 20, 2016 at 07:11:10AM -0700, Daniel J Walsh wrote:
>>
>> >Because the labels are no longer shell-processed, AFAIU.
>>
>>
On Wed, Apr 20, 2016 at 07:11:10AM -0700, Daniel J Walsh wrote:
>
> >Because the labels are no longer shell-processed, AFAIU.
>
> Is there a different way we could go about doing this? Can we create the
> container
> during the atomic install, and then just start and stop it using atomic?
We po
On 04/20/2016 06:50 AM, Jan Pazdziora wrote:
On Wed, Apr 20, 2016 at 06:24:41AM -0700, Daniel J Walsh wrote:
On 04/20/2016 05:31 AM, Jan Pazdziora wrote:
On Tue, Apr 19, 2016 at 02:02:51PM -0700, Daniel J Walsh wrote:
But I like your example better. atomic install should almost always be a
On Wed, Apr 20, 2016 at 06:24:41AM -0700, Daniel J Walsh wrote:
>
> On 04/20/2016 05:31 AM, Jan Pazdziora wrote:
> >On Tue, Apr 19, 2016 at 02:02:51PM -0700, Daniel J Walsh wrote:
> >>But I like your example better. atomic install should almost always be a
> >>privileged container.
> >I think my
On 04/20/2016 05:31 AM, Jan Pazdziora wrote:
On Tue, Apr 19, 2016 at 02:02:51PM -0700, Daniel J Walsh wrote:
But I like your example better. atomic install should almost always be a
privileged container.
I think my only concern is that RUN will have to be privileged
container (which will spa
On Tue, Apr 19, 2016 at 02:02:51PM -0700, Daniel J Walsh wrote:
>
> But I like your example better. atomic install should almost always be a
> privileged container.
I think my only concern is that RUN will have to be privileged
container (which will spawn an unprivileged one) as well because
wit
On 04/19/2016 07:21 AM, Jan Pazdziora wrote:
On Wed, Feb 17, 2016 at 10:44:52AM -0500, Daniel J Walsh wrote:
Right but your install script could communicate with docker to create a
container.
IE You separate out the act of running the install script from the
actual creation of the
container.
On Wed, Feb 17, 2016 at 10:44:52AM -0500, Daniel J Walsh wrote:
>
> Right but your install script could communicate with docker to create a
> container.
> IE You separate out the act of running the install script from the
> actual creation of the
> container.
>
> You install.sh could execute
>
>
On 02/17/2016 10:36 AM, Jan Pazdziora wrote:
> On Wed, Feb 17, 2016 at 04:25:20PM +0100, Jan Pazdziora wrote:
>> It'd be nice if the atomic command could support -h option, and make
>> that value available for use in the INSTALL / RUN / UNINSTALL LABELs.
>> I envision something like
>>
>> do
On 02/17/2016 10:25 AM, Jan Pazdziora wrote:
> Hello,
>
> with the atomic command, we can run
>
> atomic install ...
>
> to configure a service in/via a container and
>
> atomic run ...
>
> to start it.
>
> If the software in the container would like to have a particual fixed
> hostna
On Wed, Feb 17, 2016 at 04:25:20PM +0100, Jan Pazdziora wrote:
>
> It'd be nice if the atomic command could support -h option, and make
> that value available for use in the INSTALL / RUN / UNINSTALL LABELs.
> I envision something like
>
> docker install -h ipa.example.com freeipa-server --
17 matches
Mail list logo
