On 08/22/2016 06:00 PM, Josh Berkus wrote:
> Folks,
>
> Atomic CLI wraps atomicapp, so that we don't have a separate atomicapp
> command in the ADB or on Atomic Host.
>
> However, how do I handle answers.conf using the Atomic CLI? I can't
> find this in the documentation anywhere.
You should be able to do this via the --answers argument:
```
[fedora@cloudhost ~]$ sudo atomic run projectatomic/helloapache --mode=fetch
--destination ./
docker run -it --rm --privileged -v /var/home/fedora:/atomicapp -v /run:/run -v
/:/host --net=host --name helloapache -e USER -e SUDO_USER -e NAME=helloapache
-e IMAGE=projectatomic/helloapache projectatomic/helloapache run --mode=fetch
--destination ./
This container uses privileged security switches:
INFO: --net=host
Processes in this container can listen to ports (and possibly rawip
traffic) on the host's network.
INFO: --privileged
This container runs without separation and should be considered the same
as root on your system.
For more information on these switches and their security implications, consult
the manpage for 'docker run'.
INFO :: Atomic App: 0.6.2 - Mode: Fetch
INFO :: Unpacking image projectatomic/helloapache to ./
INFO :: Skipping pulling docker image: projectatomic/helloapache
INFO :: Extracting Nulecule data from image projectatomic/helloapache to ./
INFO :: Copying files from image projectatomic/helloapache:application-entity
to /tmp/nulecule-657e0170-6968-11e6-ac3d-525400926967
Your application resides in ./
Please use this directory for managing your application
[fedora@cloudhost ~]$ cp answers.conf.sample joshanswers
[fedora@cloudhost ~]$ vi joshanswers # <--- perform edits here
[fedora@cloudhost ~]$
[fedora@cloudhost ~]$ sudo atomic run projectatomic/helloapache --answers
./joshanswers ./
docker run -it --rm --privileged -v /var/home/fedora:/atomicapp -v /run:/run -v
/:/host --net=host --name helloapache -e USER -e SUDO_USER -e NAME=helloapache
-e IMAGE=projectatomic/helloapache projectatomic/helloapache run --answers
./joshanswers ./
This container uses privileged security switches:
INFO: --net=host
Processes in this container can listen to ports (and possibly rawip
traffic) on the host's network.
INFO: --privileged
This container runs without separation and should be considered the same
as root on your system.
For more information on these switches and their security implications, consult
the manpage for 'docker run'.
INFO :: Atomic App: 0.6.2 - Mode: Run
INFO :: Deploying to provider: Docker
Unable to find image 'centos/httpd:latest' locally
Trying to pull repository docker.io/centos/httpd ...
```
_______________________________________________
Container-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/container-tools
