I tried etcd from your branch  and with a single change , the etcd
system container was a drop-in replacement instead of using etcd
from the package.
 I needed to set ETCD_INITIAL_CLUSTER="" since we use
the option ETCD_DISCOVERY and they conflict.
ETCD_INITIAL_CLUSTER is coming from . Maybe we shouldn't
set all these options by default.
jasonbrooks/atomic-system-commit containers/tree/kube- containers f99eaaa7a4a74595bd1be23c470d4a b1dd1a66ddOn 3 May 2017 at 10:47, Giuseppe Scrivano <gscrivan redhat com> wrote:Hi Jason,
Jason Brooks <jbrooks redhat com> writes:
> I've experimented w/ making more changes to the ansible like these --
> adapting the scripts to the system containers rather than the reverse,
> but I started thinking it'd be easier to adapt the system containers
> to be more of a drop-in replacement, leaving them to be configured as
> much like the regular packages as possible. So, things like making
> etcd configurable by editing a conf file vs. limiting configuration to
> --set commands. Do you think it's worthwhile to try and make system
> containers work this way, or would we be losing out on some system
> containers goodness through this?
yes, this is something that was requested by different users and it
makes sense to change the etcd container to support reading its
configuration from a file as well.
Now that we support copy of files to the host, we can create this file
at installation time and still allow multiple instances of the etcd
It could be placed on the host accordingly to the container name like:
The Docker container is already using this feature:
ic/atomic-system-containers/ commit/316a5c7587648ae431b6d34 255454d407063844b
And for renaming the files (to take into account the container name):
mic-system-containers/blob/e15 222e1240131458d08b5dd85a73ffb1 652b79c/docker-centos/manifest .json
For etcd we will need to create the bind mount as well. In the Docker
case it wasn't needed since we are already bind mounting /etc.