Closed paapu88 closed 1 year ago
Hello @paapu88, thanks for reaching out. Is your uname output for the docker container or host machine? The reason I am asking is because there is an issue with our image tagging as of late. All the ARM images get uploaded after the x86 ones, and they have been overriding the latest tag in the repo. A fix for this will come shortly and you can try again with an image that properly supports x86.
All the commans and outputs are from inside of a docker container
It works now good for me outside of the docker container, was just inside docker for debugging. So for my purposes it is working fine for the moment, and you can close this issue if you find of no general value.
Thanks, will keep the issue open for now. I have tested building on the docker container myself and have not encountered such an issue yet. Will keep looking.
Describe the bug
In a docker container I run:
output
Environment (please complete the following information):
bash-4.2# uname -r 6.0.0-1006-oem
bash-4.2# uname -m x86_64
git log commit c9a337567240059a0ea9a5af91868ec775c55e47 (HEAD -> main, tag: v3.1.0, origin/main, origin/HEAD) Author: RogerZhongAWS 100961047+RogerZhongAWS@users.noreply.github.com Date: Mon Mar 6 09:09:19 2023 -0800
zlib-1.2.13 boost_1_81_0 protobuf-all-3.17.3 git checkout OpenSSL_1_1_1-stable git clone --branch v2.13.6 https://github.com/catchorg/Catch2.git