Discussions related to ansible configuration management
@s.p.i has joined the channel
@Pablo Costa has joined the channel
@mrwacky has joined the channel
@tamsky I have never used systemd in docker that is interesting idea. So to go a little deeper into how we are layering out images it goes like this base -> application -> code each of those have it’s own repository so I can update and play around with making underlaying dependencies changes in the system level stuff under application and then we always layer code over that . Last step we have tests which I am mostly using goss currently but that takes the code repo image and installs testing framework over it and runs them then that last step “could” give the green light in a CI/CD pipeline
I have never used systemd in docker that is interesting idea.
Ok article describing one group’s setup: http://t0t0.github.io/internship%20week%207/2016/03/30/cloud-config-docker.html
Toon and Tomas` blog
@ndobbs has joined the channel
@sigafoose has joined the channel
@maarten has joined the channel
set the channel topic:
@Erik Osterman (Cloud Posse) has joined the channel
set the channel description: Discussions related to ansible configuration management
@tamsky has joined the channel
@catdevman has joined the channel
@Andriy Knysh (Cloud Posse) has joined the channel
I need to put my notes together but basically I’ve been enabling the OS-default
/bin/init, after which I can test
packer->docker+systemd->ansible playbooks pipelines that install/configure system services.
CentOS publishes theirs at https://hub.docker.com/_/centos/ under “Dockerfile for systemd base image”.
Right now I’m trying to see if I can walk this strategy all the way back to
amazonlinux:1 and enable upstart.
would love to get a demo of this stuff later….
@pigglesticks has joined the channel