@jglogan Could you please take a look?

@mayooot - thanks for the PR.

From reading the original issue discussion, I think the direction suggested was to add the utility in github.com/apple/containerization since we'll also want to address this there, and then use that utility in container?

@mayooot - thanks for the PR.

From reading the original issue discussion, I think the direction suggested was to add the utility in github.com/apple/containerization since we'll also want to address this there, and then use that utility in container?

Ok, thanks for your reply. Do you have any suggestions on where to place this utility?

Do you have any suggestions on where to place this utility?

@mayooot The issue in the containerization repo is apple/containerization#255. Having it there could allow us to do the right thing for image downloads as well as kernel.

I'd start by having a look at the issue (see the comment at apple/containerization#255 (comment)) and then adapting what's in your PR to that. IMO ContainerizationExtras is the best place to put it the proxy utility.

Then this PR would just contain your kernel download fix. I'll create another issue for the image pull/push fix in container so that we can keep this PR small and quick to merge.

Added #578 for image push/pull.

Do you have any suggestions on where to place this utility?

@mayooot The issue in the containerization repo is apple/containerization#255. Having it there could allow us to do the right thing for image downloads as well as kernel.

I'd start by having a look at the issue (see the comment at apple/containerization#255 (comment)) and then adapting what's in your PR to that. IMO ContainerizationExtras is the best place to put it the proxy utility.

Then this PR would just contain your kernel download fix. I'll create another issue for the image pull/push fix in container so that we can keep this PR small and quick to merge.

Thanks a lot, I'll check it out ASAP.

For this PR, this will probably need to be fixed:

Might even be good to add a little fuzzing in the git workflow so that it randomly chooses HTTPS_PROXY or https_proxy.

@mayooot Have a go at an updated version once we merge #606. You should be able to bring in your proxy utility then.

Did you want to have a crack at apple/containerization#255 and then the container updates to use the affected image store APIs?

@mayooot Have a go at an updated version once we merge #606. You should be able to bring in your proxy utility then.

Did you want to have a crack at apple/containerization#255 and then the container updates to use the affected image store APIs?

Sure, I can take a look.