Container Minutes 11 Sep 2017 - ansible/community GitHub Wiki
Attendees:
- fabianvf
- ttomecek
- ryansb
- j00bar
- gregdek
- chouseknecht
- tima
Discussion:
-
Roadmap in relationship to 1.0.0
- j00bar suggested that we make the following roadmap items part of 1.0.0
- Create multiple, simple working examples similar to Jag's "Hello World" demo from AnsibleFest
- Get pre-baked conductor images passing RedHat Security Scan, and pushed into RedHat Container Catalog
- Create daily pre-bake, scanning, and pushing of images in Travis
- Everyone agreed. J00bar took ownership of items 1 and 3, and chouseknecht took item 2.
- chouseknecht requested a 0.9.2 release push to PyPi, so that users are using and providing feedback with latest code
- j00bar worked out a way to reduce the pre-baked images sizes, and will push this new code as part of 0.9.2 in the next day or two.
- j00bar will also look into bumping the Docker compose version requirement in
conductor-requirements.txt
. It's currently at>=1.14
. That may possibly be related to issue #720. - remaining items on the roadmap will be post 1.0.0
- j00bar suggested that we make the following roadmap items part of 1.0.0
-
- Consensus is that running
systemd
within a container and wanting the init system to own PID 1, is a valid use case. - Rather than having a single directive called
build_command
, the PR should be modified to provide a broader directive calledbuild_overrides
that follows the pattern ofdev_overrides
. - j00bar summarized,
build_overrides
is a good addition tocontainer.yml
because:- It remains consistent. Meaning, if you are familiar with a subset of our syntax, learning a new section should be intuitive.
- It's DRY.
- Every addition creates clear value.
- chouseknecht volunteered to comment on the PR.
- Consensus is that running
-
j00bar suggested that we start an "Advanced Techniques" section in the docs
- Get users started on the happy case with the low friction, shallow onramp story
- In this new section, offer solutions to problems that some users run into and need help solving
- The issue expressed in PR #719 is an example that fits in this new section