You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Mar 23, 2019. It is now read-only.
The default that was created with ansible-container init:
version: "2"
settings:
# The Conductor container does the heavy lifting, and provides a portable
# Python runtime for building your target containers. It should be derived
# from the same distribution as you're building your target containers with.
conductor_base: centos:7
# The deployment_output_path is mounted to the Conductor container, and the
# `run` and `deployment` commands then write generated Ansible playbooks to it.
# deployment_output_path: ./ansible-deployment
# When using the k8s or openshift engines, use the following to authorize with the API.
# Values set here will be passed to the Ansible modules. Any file paths will be mounted
# to the conductor container, allowing the `run` command to access the API.
#k8s_auth:
# path to a K8s config file
#config_file:
# name of a context found within the config.json file
#context:
# URL for accessing the K8s API
#host:
# An API authentication token
#api_key:
# Path to a ca cert file
#ssl_ca_cert:
# Path to a cert file
#cert_file:
# Path to a key file
#key_file:
#boolean, indicating if SSL certs should be validated
#verify_ssl:
# When using the k8s or openshift engines, use the following to set the namespace.
# If not set, the project name will be used. For openshift, the namespace maps to a project,
# and description and display_name are supported.
#k8s_namespace:
# name:
# description:
# display_name:
services: {}
# Add your containers here, specifying the base image you want to build from.
# To use this example, uncomment it and delete the curly braces after services key.
# You may need to run `docker pull ubuntu:trusty` for this to work.
# web:
# from: "centos:7"
# ports:
# - "80:80"
# command: ["/usr/bin/dumb-init", "/usr/sbin/apache2ctl", "-D", "FOREGROUND"]
# dev_overrides:
# environment:
# - "DEBUG=1"
registries: {}
# Add optional registries used for deployment. For example:
# google:
# url: https://gcr.io
# namespace: my-cool-project-xxxxxx
Seems I might be hitting this bug when trying to build a docker image from scratch with ansible installed? pypa/setuptools#964 Note: running molecule init --role foo --driver docker && molecule test works perfectly on my system.
Thanks folks. I see now that setuptools 36.0.1 was released to fix this. https:/pypa/setuptools/blob/master/CHANGES.rst (though with this installed, I'm still seeing the error. Will try upgrading ansible-container to include the fix instead.)
Edit: Yep, the above patch fixes it for me when running from source. :)
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
ISSUE TYPE
container.yml
The default that was created with
ansible-container init
:OS / ENVIRONMENT
SUMMARY
Seems I might be hitting this bug when trying to build a docker image from scratch with ansible installed? pypa/setuptools#964 Note: running
molecule init --role foo --driver docker && molecule test
works perfectly on my system.STEPS TO REPRODUCE
EXPECTED RESULTS
I'd get some kind of success or an error message relevant to my playbook and/or docker configuration.
ACTUAL RESULTS
AnsibleContainerException: Error building conductor image: The command '/bin/sh -c cd /_ansible && pip install -r container/conductor-build/conductor-requirements.txt && PYTHONPATH=. LC_ALL="en_US.UTF-8" python container/conductor-build/setup.py develop -v && ansible-galaxy install -p /etc/ansible/roles -r container/conductor-build/conductor-requirements.yml' returned a non-zero code: 1
Where the debug output shows
ImportError: No module named six
. The full output is below:debug-output.txt
The text was updated successfully, but these errors were encountered: