RHCOS multi-arch builder splunkforwarder container fails to build #1044
Comments
|
+1 |
marmijo
added a commit
to marmijo/fedora-coreos-pipeline
that referenced
this issue
Oct 8, 2024
The repo we are using to build the ITPAAS splunkforwarder container on the RHCOS multi-arch builders is out of date and references a splunkforwarder rpm that no longer exists in the internal repos. By omitting the build step for this container, we can pull in the already built image from ITPAAS that includes a more recent RPM. We'll still use `--arch=x86_64` for the sidecar container to ensure proper logging on non x86_64 builders. See: coreos#1044
marmijo
added a commit
to marmijo/fedora-coreos-pipeline
that referenced
this issue
Oct 8, 2024
The repo we are using to build the ITPAAS splunkforwarder container on the RHCOS multi-arch builders is out of date and references a splunkforwarder rpm that no longer exists in the internal repos. By omitting the build step for this container, we can pull in the already built image from ITPAAS that includes a more recent RPM. We'll still use `--arch=x86_64` for the sidecar container to ensure proper logging on non x86_64 builders. See: coreos#1044
|
PR to update the butane config for the multi-arch builders to stop building the ITPAAS base splunkforwarder container and build only the splunk sidecar container: #1045 |
marmijo
added a commit
that referenced
this issue
Oct 8, 2024
The repo we are using to build the ITPAAS splunkforwarder container on the RHCOS multi-arch builders is out of date and references a splunkforwarder rpm that no longer exists in the internal repos. By omitting the build step for this container, we can pull in the already built image from ITPAAS that includes a more recent RPM. We'll still use `--arch=x86_64` for the sidecar container to ensure proper logging on non x86_64 builders. See: #1044
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
The splunkfowarder container on the RHCOS multi-arch builders has been failing to build due to multiple reasons. Mainly because the internal gitlab repos being used are outdated and the version of the splunkforwarder package being installed is no longer available in the internal repos.
We should stop building the base splunkforwarder image on the remote builders and instead just pull the image provided by IT, which has the newer splunk package already installed.
See: https://issues.redhat.com/browse/COS-2966
The text was updated successfully, but these errors were encountered: