-
Notifications
You must be signed in to change notification settings - Fork 997
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to build OPA from source in docker #9466
Labels
Projects
Comments
BbolroC
added
bug
Incorrect behaviour
needs-review
Needs to be assessed by the team.
labels
Apr 12, 2024
3 tasks
BbolroC
added a commit
to BbolroC/kata-containers
that referenced
this issue
Apr 16, 2024
The commit is to make the OPA build from source working in `ubuntu-rootfs-osbuilder`. To achieve the goal, the configuration is changed as follows: - Switch the make target to `ci-build-linux-static` not triggering another docker build - Install go in the builder image for s390x and ppc64le Fixes: kata-containers#9466 Signed-off-by: Hyounggyu Choi <Hyounggyu.Choi@ibm.com>
BbolroC
added a commit
to BbolroC/kata-containers
that referenced
this issue
Apr 16, 2024
…c64le The commit is to make the OPA build from source working in `ubuntu-rootfs-osbuilder`. To achieve the goal, the configuration is changed as follows: - Switch the make target to `ci-build-linux-static` not triggering another docker build - Install go in the builder image for s390x and ppc64le Fixes: kata-containers#9466 Signed-off-by: Hyounggyu Choi <Hyounggyu.Choi@ibm.com>
BbolroC
added a commit
to BbolroC/kata-containers
that referenced
this issue
Apr 16, 2024
The commit is to make the OPA build from source working in `ubuntu-rootfs-osbuilder`. To achieve the goal, the configuration is changed as follows: - Switch the make target to `ci-build-linux-static` not triggering docker-in-docker build - Install go in the builder image for s390x and ppc64le Fixes: kata-containers#9466 Signed-off-by: Hyounggyu Choi <Hyounggyu.Choi@ibm.com>
BbolroC
added a commit
to BbolroC/kata-containers
that referenced
this issue
Apr 16, 2024
The commit is to make the OPA build from source working in `ubuntu-rootfs-osbuilder`. To achieve the goal, the configuration is changed as follows: - Switch the make target to `ci-build-linux-static` not triggering docker-in-docker build - Install go in the builder image for s390x and ppc64le Fixes: kata-containers#9466 Signed-off-by: Hyounggyu Choi <Hyounggyu.Choi@ibm.com>
BbolroC
added a commit
to BbolroC/kata-containers
that referenced
this issue
Apr 16, 2024
The commit is to make the OPA build from source working in `ubuntu-rootfs-osbuilder`. To achieve the goal, the configuration is changed as follows: - Switch the make target to `ci-build-linux-static` not triggering docker-in-docker build - Install go in the builder image for s390x and ppc64le Fixes: kata-containers#9466 Signed-off-by: Hyounggyu Choi <Hyounggyu.Choi@ibm.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description of problem
#7769 does not seem to be merged with the verification where an OPA binary is built from source in the docker builder.
The following issue was observed:
ubuntu-rootfs-osbuilder
ci-go-ci-build-linux-static
spins another docker container which leads to thedocker-in-docker
envThe tool should be successfully built in the docker builder for s390x and ppc64le for confidential containers.
The text was updated successfully, but these errors were encountered: