-
-
Notifications
You must be signed in to change notification settings - Fork 101
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
missing nonintel docker providing machine #3482
Comments
For aarch64 we should be able to use the newer OSUOSL ones. |
Checking to see if docker is installed
|
So the question is which machines should have the |
Related (and possible duplicate) #1044 |
dockerhost machines should not be used for test, so they would not typically have |
Running some external tests on the machines which have docker installed, have the ci.role.test label and should (but not cuurently) have the sw.tool.docker label test-aws-rhel8-x64-1 https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_x86-64_linux/647/console
Having trouble connecting to the docker daemon test-osuosl-ubuntu2004-ppc64le-1 https://ci.adoptium.net/job/Test_openjdk11_hs_sanity.external_ppc64le_linux/13/console
Fails during the docker build, at what looks like a package install test-rise-ubuntu2310-riscv64-1 https://ci.adoptium.net/job/Test_openjdk21_hs_sanity.external_riscv64_linux/23/console
Needs a sudo password to proceed Am I running these wrong? ping @smlambert |
There are no nodes with the label 'ci.role.test&&sw.os.linux&&hw.arch.aarch64&&sw.tool.docker'
when attemted to run external tests out of intel.Please put the name of the software product (and affected platforms if relevant) in the title of this issue: docker on non intels, namely on aarch64
When one want to run external tests - or anything else rwquiring docker - they are moreover limited to linux intel. At least aarch64 linuxes, should be also prosion-able
It wouldbe nice, if those new installs would already provide podman out of the box, with just docker wrapper.
The text was updated successfully, but these errors were encountered: