Make sure that the name used in the changelog file is correct, and matches your intended image name."git status" in integration/config should show a change to the changelog file for the image you are updating.If you don't see any output in between "Step 1: building images" and "Step 2: publishing", this means docker-pkg did not find any images or did not find images that have unbuilt newer versions. To workaround this issue, run the following in your Terminal window before running a docker-pkg command: OSError: Could not find a suitable TLS CA certificate bundle, invalid path: /etc/ssl/certs/ca-certificates.crt The following error is known to affect macOS: ERROR - Could not load image in integration/config/dockerfiles/…: Could not find a suitable TLS CA certificate bundle, invalid path: /etc/ssl/certs/ca-certificates.crt (builder.py:244)įile "/usr/local/lib/python3.7/site-packages/requests/adapters.py", line 228, in cert_verify Troubleshooting Could not find a suitable TLS CA certificate bundle NOT publishing images as we have no auth setup => Building image /releng/ci-jessie:0.3.0 => Building image /releng/operations-puppet:0.1.0 => Building image /releng/ci-stretch:0.1.0
$ docker-pkg -c dockerfiles/config.yaml build dockerfiles
DOCKER FOR MAC INSTALL CERTIFICATE CODE
These images are created from Dockerfiles in the integration/config.git repository.ĭocker-pkg is a python3 program that is used to build Docker images, with Jinja for additional templating.Ĭlone the code from docker-pkg and install via pip3: The Docker images for CI are published at under the releng namespace. The behaviour of the container should rely only on environment variables provided by Jenkins ( ZUUL_URL, ZUUL_REF, etc). The containers you create should be self-sufficient and leave nothing behind, except logs. 2.3.1 Could not find a suitable TLS CA certificate bundleĪdministrative tasks are currently handled solely by Jenkins.
0 kommentar(er)
