-
Notifications
You must be signed in to change notification settings - Fork 558
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
Unable to download debian packages from self hosted runners #884
Comments
Looks like docker is not properly installed on your self-hosted runner: https://github.com/hoprnet/hoprnet/actions/runs/5321651593/jobs/9637024279#step:7:18
Client version is |
Thanks for pointing that, I've fixed the mismatching version on self-hosted runners, nevertheless doesn't seem to be the root cause. After changing the runners docker version is still not working. Another interesting topic is that the raw docker command does not work either so I will focus more in the configuration of the self-hosted runners |
Looks like an issue with your self-hosted. Closing as it does not seem related to the action. |
Hi @crazy-max ,
|
Troubleshooting
Behaviour
I cannot build a simple docker image using self hosted runners because access to http://deb.debian.org/debian/dists/bullseye/InRelease is failing due to a timeout
Steps to reproduce this issue
Expected behaviour
I would expect the networking to be working the same from outside the docker container.
Actual behaviour
As it can be seen from the github workflow provided, the job has internet access and is able to get the contents of the above mentioned URL.
As it can be seen from the logs, the command
RUN curl http://www.ifconfig.me
works fine so means that from within the container is also able to download things.But when executes the second command
RUN curl -v http://deb.debian.org/debian/dists/bullseye/InRelease
it fails due to a timeout.The reason for executing this command is because it is internally executed by the
RUN apt-get update
command.Configuration
Dockerfile
Workflow
Logs
The text was updated successfully, but these errors were encountered: