Failed to create a build container
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| StarlingX |
New
|
Low
|
Unassigned | ||
Bug Description
Brief Description
-----------------
stx-init-env --rebuild sometimes fails due to issues connecting to various software source that contribute to building of the build containers. This seems to be much more common in the early morning hours (~2 am EST).
Ideally, CENGN has a mirror of all of these inputs. Can we modify the Dockerfiles to pull from CENGN if the primary source is down or unreachable?
Severity
--------
Minor
Steps to Reproduce
------------------
stx-init-env --rebuild
Expected Behavior
------------------
Build containers created successfully
Actual Behavior
----------------
Failure to create build containers
Reproducibility
---------------
Intermittent, but rare <1%
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
20221116T070000Z
Last Pass
---------
20221115T070000Z
Timestamp/Logs
--------------
02:15:38 + ./stx-init-env --rebuild
...
02:18:25 Successfully tagged stx-builder:
02:18:25 built image stx-builder:
02:18:25 Sending build context to Docker daemon 317.4kB
02:18:26 Step 1/19 : FROM debian:bullseye
...
02:20:35 Step 5/19 : RUN cd /tmp && wget http://
02:20:35 ---> Running in aa077b054066
02:20:35 [91m--2022-11-16 07:20:32-- http://
02:20:35 Resolving snapshot.debian.org (snapshot.
02:20:35 Connecting to snapshot.debian.org (snapshot.
02:21:43 [0m[91mHTTP request sent, awaiting response... [0m[91m503 Backend fetch failed
02:21:43 [0m[91m2022-11-16 07:21:32 ERROR 503: Backend fetch failed.
02:21:43
02:21:43 [0mThe command '/bin/sh -c cd /tmp && wget http://
Test Activity
-------------
Build
Workaround
----------
retry stx-init-env after waiting for connectivity to the upstream source to been restored.
| summary: |
- Failed to creat a build container + Failed to create a build container |
| Changed in starlingx: | |
| importance: | Undecided → Low |
| tags: | added: stx.build |
