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.
version: "2"
# This is the docker-container config file. For more info check http://docs.ansible.com/ansible-container/
settings:
conductor:
# 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.
base: ubuntu:xenial
roles_path: # Specify a local path containing Ansible roles
- ./roles/java_service
# volumes: # Provide a list of volumes to mount
# environment: # List or mapping of environment variables
# Set the name of the project. Defaults to basename of the project directory.
# For built services, concatenated with service name to form the built image name.
project_name: smart-platform
# 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
services:
gateway:
from: store/oracle/serverjre:8
roles:
- role: java_service
vars:
service: smart-platform-gateway-service
service_name: "Gateway"
service_description: "Smart Platform Gateway service"
environment:
AWS_SESSION_TOKEN: "{{ aws_session_token }}"
AWS_ACCESS_KEY_ID: "{{ aws_access_key_id }}"
AWS_SECRET_ACCESS_KEY: "{{ aws_secret_access_key }}"
command: [/app/run_service.sh]
entrypoint: [/usr/bin/entrypoint.sh]
network_mode: "host"
stf:
from: store/oracle/serverjre:8
roles:
- role: java_service
vars:
service: supply-traffic-filtering-service
service_name: "STF"
service_description: "Supply Traffic Filtering service"
environment:
AWS_SESSION_TOKEN: "{{ aws_session_token }}"
AWS_ACCESS_KEY_ID: "{{ aws_access_key_id }}"
AWS_SECRET_ACCESS_KEY: "{{ aws_secret_access_key }}"
command: [/app/run_service.sh]
entrypoint: [/usr/bin/entrypoint.sh]
network_mode: "host"
dtf:
from: store/oracle/serverjre:8
roles:
- role: java_service
vars:
service: demand-traffic-filtering-service
service_name: "DTF"
service_description: "Demand Traffic Filtering service"
environment:
AWS_SESSION_TOKEN: "{{ aws_session_token }}"
AWS_ACCESS_KEY_ID: "{{ aws_access_key_id }}"
AWS_SECRET_ACCESS_KEY: "{{ aws_secret_access_key }}"
command: [/app/run_service.sh]
entrypoint: [/usr/bin/entrypoint.sh]
network_mode: "host"
We are using ansible playbook to create docker images for our services. For conductor we image ansible/container-conductor-ubuntu-xenial:0.9.2 from dockerhub. Our services are created from /store/oracle/serverjre image.
We experience non-deterministic behavior while running ansible-container build; there is a chance that building will get stuck (this image displays point where it gets stuck: https://imgur.com/gChyVXI).
Command which is executed is given below: ansible-container build --no-cache --services {{ component }}
In order to solve this problem, we have to stop execution (i.e. Ctrl+C it) and rerun again. It has approximately 40% chance to get stuck. Even if we build different services, behavior is non-deterministic.
After debugging, we realized that process gets stuck at this line of code:
I am willing to provide additional information regarding this problem if needed.
There was one machine, which is not available at the moment, which did not get stuck during build process. All other machines (mac OS, Ubuntu) fail unfortunately.
ISSUE TYPE
container.yml
OS / ENVIRONMENT
SUMMARY
We are using ansible playbook to create docker images for our services. For conductor we image
ansible/container-conductor-ubuntu-xenial:0.9.2
from dockerhub. Our services are created from/store/oracle/serverjre
image.We experience non-deterministic behavior while running
ansible-container build
; there is a chance that building will get stuck (this image displays point where it gets stuck: https://imgur.com/gChyVXI).Command which is executed is given below:
ansible-container build --no-cache --services {{ component }}
In order to solve this problem, we have to stop execution (i.e. Ctrl+C it) and rerun again. It has approximately 40% chance to get stuck. Even if we build different services, behavior is non-deterministic.
After debugging, we realized that process gets stuck at this line of code:
ansible-container/container/core.py
Line 709 in 9250b44
STEPS TO REPRODUCE
Run:
ansible-container build --no-cache --services {{ component }}
within ansible playbook, until it gets stuck.EXPECTED RESULTS
Image should be built in deterministic behavior.
ACTUAL RESULTS
Image building sometimes gets stuck.
The text was updated successfully, but these errors were encountered: