This repository has been archived by the owner on Apr 14, 2023. It is now read-only.
Running Walkoff using a proxy failes to retrieve images #247
Comments
|
make sure you run with the "--build" parameter for the first time, it appears that the bootloader images wasn't built. running up with --build should resolve. |
|
@g0es Thanks for your hint, but I did this without succcess. Do you have any futher trick? |
|
@crackytsi, I am using the latest version and it builds the containers properly on OS X and Ubuntu. What os are you running the build script from? Have you tried to down walkoff with the cleanup flag? I would then clean up docker images associated with Walkoff before building again.
|
|
I get the following error Details: |
|
@crackytsi it looks like the host you are running walkoff on is having issues retrieving |
|
@g0es You are right, the issue is related to proxy support. I tested it without proxy on an interface facing machine and it works there. |
crackytsi
changed the title
Just to be sure, you're referring to the procedure in https://docs.docker.com/network/proxy/, right? These are handled by Docker, Walkoff itself doesn't know what to do with them.
Where/when does it fail? Can you share the output/errors? |
|
1Yes, I did it exactly this way. |
|
If I remember corectly it is a problem of the apt-key, resp. gpg ignoring the proxy settings. I was able to overcome it by modifying the Dockerfile and adding the --keyserver-options http-proxy=<yout_proxy_here> to the apt-key line https://unix.stackexchange.com/questions/361213/unable-to-add-gpg-key-with-apt-key-behind-a-proxy |
|
I ran into a slew of issues installing WALKOFF behind a corporate proxy. Sometimes it was needing to specify the proxy in the Dockerfile and sometimes it was adding my root ca to the container. Here are a few suggestions that helped me: ENV http_proxy http://(your proxy):(your proxy port) In the bootloader Dockerfile, for example, I added those lines in the Copy pip packages and source files section before the RUN commands. Was a bit of a pain, as I had do do this for almost all of the Dockerfiles. I didn't thoroughly document which ones and where I had to do that, lots of trial and error, but hope this suggestion helps. |
|
Hi @crackytsi, First, thank you all for all of your inputs. I've ran through the exact same issue and here is how I fixed it. You need to modify line 23 of as well as modify the config file of docker located at The bootloader/Dockerfile will correctly execute once you restart the docker service. However, this does not work for the rest of the installation. You might encounter same struggles during the UMPIRE step. So I recommend forcing ENV values in every Dockerfiles as a quick fix. It worked for me. Here is a list of the files you might need to set ENV values : |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Hi,
The latest version does not work, because of missing docker image.
Error:
Unable to find image 'walkoff_bootloader:latest' locally
docker: Error response from daemon: pull access denied for walkoff_bootloader, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.
The text was updated successfully, but these errors were encountered: