Another in a series of “state-of-development-consciousness” blog posts. In this one, we try to update the AnsibleContainer project for the CODE-RADE build containers.

:tomato: 1

Now playing “Backlash”, by Black Joe Lewis and the Honeybears

  • Create a new branch of the repo
  • Clean out container.yml to contain just one of the services.
  • Pull base containers from
  • There seems to be a change in the way the data volumes are handled

The data volumes needed are to provide persistence across builds and sites for build products, modulefiles, setup files, etc. This was previously done using volumes_from directives in the services, and data-volume containers were created from the smallest possible base (alpine). Now, we have the pure data container pattern, so we need to create the volume itself, not the container with the data volume. On my laptop there are several data volumes, but the ansile_CODE-RADE-xyz data volumes are basically empty :

8.0K	ansible_CODE-RADE-cvmfs_1
8.0K ansible_CODE-RADE-modules_1
8.0K ansible_CODE-RADE-repo_1
8.0K ansible_CODE-RADE-soft_1
8.0K ansible_CODE-RADE-src_1
  • In the spirit of cleaning out everything - nuke ALL the data volumes ! (bonus side-effect - cleaned out 20GB)
  • Started first build attempt

:tomato: 2

“Return to the 37th”, by El Michaels Affair

  • Read the Docker volume documentation for v2
  • Declare top-level directive volume with just the name and driver.
  • Tried second attempt - missing dependencies in the virtualenv, installed them. CEntOS6 base image not giving any :heart:, so moved to CEntOS7 for now.

:tomato: 3

“Eastbound”, the Budos Band

  • CEntOS7 image is built and can run.
  • SSH Host Key has changed. No damn good ! We need to change the tasks in the role… time to get back to dev.

:tomato: 4

“Crush” by Lettuce

  • Remove the ssh host key generation task from the role
  • Pre-generate ssh keys for RSA, DSA and ECDSA keys
  • Add tasks to copy these to the SSH directory of the endpoint

:tomato: 5

Complete Mythology”, by Syl Johnson

  • We can’t add the private keys to the repo in clear text, so we need to encrypt them with vault. Check the Ansible documentation to see if vault is supported… seems to be.
  • move to a new branch (static-host-keys)
  • Before we go full-hog encrypting all the things, let’s see if this update will pass a molecule test… (there goes the :tomato: - these builds take a while)
  • Builds are passing (CEntOS7 at least) - let’s see if we can encrypt them and test the role with molecule - ansible-vault encrypt files/etc/ssh/<key-file>

:tomato: 6

“Nude & Rude”, by Iggy Pop

  • How do we tell molecule about the vault password now ? Here’s how - TL;DR: provisioner.options
  • Well… neither the Ansible Container documentation for vault nor the molecule documentation for vault is working. Tried the vault password in a file, but neither the environment variable ANSIBLE_VAULT_PASSWORD_FILE nor --vault-password-file flag seem to work.
  • I guess I can test the image build locally and push to the registry so that we can see if Jenkins is happier.

Build attempts

Attempt 1


from: ""
privileged: true
- ansible_CODE_RADE-src_1:/data/src
- AAROC.CODE-RADE-container
- "5000:5200"
command: ["/usr/sbin/sshd", "-D","-p","5200"]

- /data/src

This gave error :

ERROR The container.yml file is invalid: ['/data/src'] is not of type 'object'

Attempt 2

Hit this issue.

CEntOS6 image not working. This is also referenced in an issue opened by Jenkins during a previous build.


Vault with Ansible Container is not working for me. Doing things properly,

  • I need to encrypt the private keys so that
  • I can commit them somewhat safely to the repo so that
  • Ansible Galaxy can find the role so that
  • Ansible Container can use the role

I can circumvent that for the moment by using --roles-path and not requring anything to be pushed to the repo. That would be cheating.