# Minutes from Ansible Container WG meeting, 31 July, 2017 **URL:** \ **Category:** Ansible Developer\ **Created:** [August 7, 2017, 3:53pm UTC](https://forum.ansible.com/t/minutes-from-ansible-container-wg-meeting-31-july-2017/25195 "2017-08-07T15:53:31Z")\ **Posts on this page:** 1\ **Page:** 1
**Author:** ![Joshua\_jag\_Ginsberg](https://avatars.discourse-cdn.com/v4/letter/j/bc79bd/32.png) [@Joshua\_jag\_Ginsberg](https://forum.ansible.com/u/Joshua_jag_Ginsberg)\ **Post date:** [August 7, 2017, 3:53pm UTC](https://forum.ansible.com/t/minutes-from-ansible-container-wg-meeting-31-july-2017/25195/1 "2017-08-07T15:53:31Z")
Apologies for the delay in getting these out, but here are the minutes from the first Ansible Container WG meeting from last Monday. I hope y’all had a great weekend! Present: gregdek j00bar chouseknecht ryansb ttomecek fvonfeil ehelms tima jlk Lurking: funzo jmrodri Topics: The Road to Ansible Container 1.0 - Where are we with the prebaked conductors? - ryansb has changes to j00bar’s branch. Wants to close the PR and rebase. - ryansb has concerns about testing images before they ship - believes we have to cut a new CLI version to update prebaked conductors - j00bar says we do not - we can repush under the same label matching ansible-container version - chouseknecht points out we will have to push images every time we make a release though - j00bar agrees - gregdek says we can cut another 0.9.x release prior to 1.0 for testing prebake - chouseknecht asks if the ansible-container code will be baked into the prebaked conductors; j00bar says yes. - gregdek asks if we assume “:latest” tag on images; ryansb says we do not, that we label with **version** from ansible-container code - gregdek asks about user-submitted conductors. j00bar and ryandb respond that users can bring their own conductor still and that we’re always open to more supported prebakes if we missed a popular base image - Other show stoppers? - j00bar really wants to get “the shim” done - a wrapper around the python execution to better seamlessly support py3 build targets - j00bar believes issue #564 ([https://github.com/ansible/ansible-container/issues/564](https://github.com/ansible/ansible-container/issues/564)) is a show-stopper - gregdek says the issue has been closed and the milestone it belongs to closed as well - j00bar says it looks like we need to increment the version of docker-py and we should be good - tima points out we should have a blog post ready for the next release and gregdek agrees The Buildah engine - ttomecek - the core.py implementation is too Docker specific. j00bar agrees to help refactor. Lightbulb for Ansible Container - tima wants an iterative walkthrough to make a deck/demos for self-learning as well as SAs or motivated community members at meetups to use - gregdek suggests taking the existing ansible-container-demo and walking backward from there Administrivia - We need to get setup on ansible/community on GitHub for this WG. It will be divyed up between tima and ryansb.