Skip to content
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

centos7_docker_image_updater failing on RISC-V #3550

Open
sxa opened this issue May 3, 2024 · 4 comments
Open

centos7_docker_image_updater failing on RISC-V #3550

sxa opened this issue May 3, 2024 · 4 comments

Comments

@sxa
Copy link
Member

sxa commented May 3, 2024

Ref: https://ci.adoptium.net/job/centos7_docker_image_updater/504/execution/node/89/log/

+ docker build -t adoptopenjdk/ubuntu2004_build_image:linux-riscv64 --build-arg git_sha=2a029fd406c6f35f70c32ef5a814933fa11297ee -f ansible/docker/Dockerfile.Ubuntu2004-riscv64 .
ERROR: permission denied while trying to connect to the Docker daemon socket at unix:///var/run/docker.sock: Get "http://%2Fvar%2Frun%2Fdocker.sock/_ping": dial unix /var/run/docker.sock: connect: permission denied

Runs on docker&&linux&&riscv64 and has selected Scaleway machine 1 for that particular run

@sxa
Copy link
Member Author

sxa commented May 3, 2024

I've restarted the jenkins agent on the -1 machine in case it wasn't in the correct docker group before. I've been able to run docker operations from the jenkins user on the command line without issues, so hopefully it will be ok.
Looking at -8 it is in a similar situation where running id from the jenkins script console shows that it is NOT in the docker group, but logging into the machine.

All of the others seemed similar - I verified 2 and, 8. On that basis I've restarted the agent on each of the boards 1 through 10

Noting that not all of them enabled the docker group after the restart so potentially additional remediation will be required on the machines.

@sxa
Copy link
Member Author

sxa commented May 3, 2024

I've switched docker and dockerBuild for dockerX and dockerBuildX to avoid problems until someone can fix this on the machines.

@sxa
Copy link
Member Author

sxa commented Dec 16, 2024

Memo to self: Retry when the machines are refreshed as a part of #3719

@sxa
Copy link
Member Author

sxa commented Jan 2, 2025

Removing from the current plan on the assumption that this will get resolved as part of the reinstalls in #3719

@sxa sxa removed this from the 2024-12 (December) milestone Jan 2, 2025
@sxa sxa moved this from Todo to Paused/Blocked in Adoptium Backlog Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
Status: Paused/Blocked
Development

No branches or pull requests

1 participant