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
Ensure we use the sw.tool.docker label for machines with Docker installed, not for nodes that are themselves containers. This label is used by tests that require docker or podman and typically will not run inside a container (docker in docker).
smlambert
changed the title
Some Jenkins nodes with sw.tool.docker seem to be docker containers
Some Jenkins nodes with sw.tool.docker label seem to be docker containers
Nov 23, 2022
I've just logged into all three of those systems and been able to start up a docker container on each of them so I'm not clear on what the problem is on those systems - have you seen something to indicate the labels on those three machines are not accurate, or had a failure to run as expected on those hosts?
I assumed given the naming that those hosts were themselves docker containers, and there is a note regarding the containers tests being added by @jerboaa that they may not run well container in container (related: adoptium/aqa-tests#4143 (comment)). So, while I have not tried those tests on these machines, I raised the issue in case it's a real concern.
Ensure we use the sw.tool.docker label for machines with Docker installed, not for nodes that are themselves containers. This label is used by tests that require docker or podman and typically will not run inside a container (docker in docker).
3 nodes in question are
docker-osuosl-ubuntu2004-ppc64le-1
docker-skytap-ubuntu2004-ppc64le-1
dockerhost-osuosl-ubuntu2204-aarch64-1
Related to #93
The text was updated successfully, but these errors were encountered: