[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]
Re: [atomic] passing ENV though atomic
- From: Josh Berkus <jberkus redhat com>
- To: solarflow99 <solarflow99 gmail com>
- Cc: atomic projectatomic io
- Subject: Re: [atomic] passing ENV though atomic
- Date: Wed, 22 Feb 2017 14:34:42 -0800
On 02/22/2017 02:19 PM, solarflow99 wrote:
> yes,
>
> On Wed, Feb 22, 2017 at 2:03 PM, Josh Berkus <jberkus redhat com
> <mailto:jberkus redhat com>> wrote:
>
> On 02/22/2017 01:50 PM, solarflow99 wrote:
> > The RUN line is exactly the same as the docker run line in the unit file
> > has: ExecStart=/usr/bin/docker run -dp 192.168.10.213:80:80 --name=dash
> > The only difference it doesn't work when invoking it from "atomic run"
> > It looked like it might have been the Environment wasn't getting
> > through since I would see a permission denied for .docker in journalctl
> > The line commented out it the only way it works, if I uncomment and use
> > that instead of atomic run. wierd.
> >
>
>
> Does it work if you use atomic run interactiely?
Why does having $HOME set make a difference for this container? That
ENV is outside the container, not inside of it.
(p.s. try #atomic on Freenode IRC for more interactive help)
--
--
Josh Berkus
Project Atomic
Red Hat OSAS
[Date Prev][Date Next] [Thread Prev][Thread Next]
[Thread Index]
[Date Index]
[Author Index]