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 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.
I forgot to add -- that would remove the need for that "driving"
privileged container in RUN and the LABEL RUN command could be
unprivileged.
--
Jan Pazdziora
Senior Principal Software Engineer, Identity Management Engineering, Red Hat
