Failed to build xen-tools about eve

[jren1]

All the eve pkgs are built with alpine Linux in Docker, including xen-tools. I tried to modify the pkg/xen-tools/Dockerfile to export GIT_PROXY_COMMAND to use git proxy, but it didn't work. It looks like alpine Linux doesn't support git proxy well.

Currently I have to use my personal home machine to build EVE, where there is no firewall. It will be nice if we can build EVE behind the firewall, after all the companies will have the firewall.

[deitch]

@jren1 it looks like git pulls are used throughout the Xen build process.

Assuming we can get it to work via proxy, at least manually, we can standardize it into the Dockerfile. How did you set the GIT_PROXY_COMMAND when it didn't work?

[deitch]

Just for a note for later. Assuming we can get this to work through a proxy, we have several issues to resolve:

• setting the proxy correctly in pkg/xen-tools/Dockerfile. The proxy command itself needs to be inside the container for it to work.
• the setting needs to be run-dependent (@jren1 uses it when he runs, I do not), so it cannot be permanently checked in, rather must be env or flag enabled
• our "caller" for docker build is lkt pkg build, which does not really support build args (see this issue just opened), so we cannot use build-args to pass it in

Those only come to play once we can get it running by manually setting it, waiting for @jren1 to respond to this

[deitch]

@jren1 can we close this one out? We now have full support for http_proxy,https_proxy,all_proxy,no_proxy in building the builder and in building pkg/xen-tools.

Please validate if it works. If yes, let us close it; if not, let's figure out what is missing and get it in.

[deitch]

@jren1 confirmed by email that the proxies are, indeed, passed through.

Remaining is how to configure the git proxy script as an option.

[deitch]

As I understand it, @jren1 , you have it set up to do the following:

• have a proxy script (I think you are using this that conforms to the git proxy requirements
• install that proxy in the image using COPY oe-git-proxy / in the Dockerfile
• Set GIT_PROXY_COMMAND=/oe-git-proxy env var, so that git uses that proxy script
• The git proxy script then uses all_proxy env var to access via the proxy

1. Is that correct?
2. Is it fair to say that if we had it set up so that if all_proxy was set, it would set the GIT_PROXY_COMMAND to that file, that it would work?

Please confirm and we will get it in.

[jren1]

yes, right. To make the proxy work, 2 steps are required:

1. pass the all_proxy variable to the Dockerfile
2. copy oe-git-proxy to the docker and export GIT_PROXY_COMMAND to use oe-git-proxy

Anyway, once you cooked the patch, I can help verify.

[deitch]

See #255. That should finally close this out. :-)

[jren1]

Confirmed it works behind the firewall , good job!