Brief Description
-----------------
A single use can't build stx docker images in parallel. When two jenkins jobs tried to invoke
build-stx-images.sh in parallel, building in different environments and on different branches, on failed with ...
docker: Error response from daemon: Conflict. The container name "/jenkins_update_img" is already in use by container "1932b698d2009848fd9f8912467d9c637c72b9bd45d212ac10f7b0aec2f1cebd". You have to remove (or rename) that container to be able to reuse that name.
The issue is the use of "${USER}_update_img" as a name for a temporary image. It is not unique when a single user is building in parallel. Perhaps add the pid to the image name like this ..."${USER}_$$_update_img" ... to make it unique.
Severity
--------
Major. Random image build failures for jenkins, or other power users
Steps to Reproduce
------------------
A single user sets up two independent build environments on the same system.
Both run build-stx-images.sh in parallel.
Expected Behavior
------------------
images build
Actual Behavior
----------------
One og the builds fails sporadically.
Timestamp/Logs
--------------
Successfully tagged jenkins/tis-networking-avs-heat:WRO-dev-centos-stable-build
docker: Error response from daemon: Conflict. The container name "/jenkins_update_img" is already in use by container "1932b698d2009848fd9f8912467d9c637c72b9bd45d212ac10f7b0aec2f1cebd". You have to remove (or rename) that container to be able to reuse that name.
See 'docker run --help'.
Failed to add apache workaround for tis-networking-avs-heat... Aborting
Brief Description
-----------------
A single use can't build stx docker images in parallel. When two jenkins jobs tried to invoke
build-stx-images.sh in parallel, building in different environments and on different branches, on failed with ...
docker: Error response from daemon: Conflict. The container name "/jenkins_ update_ img" is already in use by container "1932b698d20098 48fd9f8912467d9 c637c72b9bd45d2 12ac10f7b0aec2f 1cebd". You have to remove (or rename) that container to be able to reuse that name.
The issue is the use of "${USER} _update_ img" as a name for a temporary image. It is not unique when a single user is building in parallel. Perhaps add the pid to the image name like this ..."${USER} _$$_update_ img" ... to make it unique.
Severity
--------
Major. Random image build failures for jenkins, or other power users
Steps to Reproduce
------------------
A single user sets up two independent build environments on the same system.
Both run build-stx-images.sh in parallel.
Expected Behavior
------------------
images build
Actual Behavior
----------------
One og the builds fails sporadically.
Reproducibility
---------------
25%
System Configuration ------- ------
-------
N/A
Branch/Pull Time/Commit ------- ------- --
-------
2020-06-20
Last Pass
---------
2020-06-19
Timestamp/Logs tis-networking- avs-heat: WRO-dev- centos- stable- build update_ img" is already in use by container "1932b698d20098 48fd9f8912467d9 c637c72b9bd45d2 12ac10f7b0aec2f 1cebd". You have to remove (or rename) that container to be able to reuse that name. avs-heat. .. Aborting
--------------
Successfully tagged jenkins/
docker: Error response from daemon: Conflict. The container name "/jenkins_
See 'docker run --help'.
Failed to add apache workaround for tis-networking-
Test Activity
-------------
Build
Workaround
----------
Do not build in parallel.