You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Thanks for trying and glad you made some progress.
I managed to get past the above error by adding gpg
Makes sense, looks like the tests/Dockerfile.ubuntu-focal is missing that.
Where do the errors related to go come from? Do they matter if I only need to build the sysbox-test-amd64 image?
Not quite sure where the bash: go: command not found errors are coming from, but they are not critical and should not matter (you can ignore them). I think it's looking for go to be installed on the host somehow, but that means there's a mistake somewhere because all golang dependencies should be solely within the container we use to build & test Sysbox.
This issue is similar to sysbox-in-docker does not work on ubuntu-focal without some Dockerfile changes which I opened previously
Describe the issue as clearly and completely as possible.
I finally got around to following the advice here and looking through the developers-guide on how to use the Makefile
Running the following commands
gives me the following error
Include information about the host's Linux version (e.g., lsb_release, uname -a).
Workaround
Similar to sysbox-in-docker does not work on ubuntu-focal without some Dockerfile changes, I managed to get past the above error by adding
gpg
to tests/Dockerfile.ubuntu-focal but then I got the following errorwhich I then got past by changing ARG crio_os=xUbuntu_22.04 to
ARG crio_os=xUbuntu_20.04
Where do the errors related to
go
come from? Do they matter if I only need to build thesysbox-test-amd64
image?The text was updated successfully, but these errors were encountered: