Paul "TBBle" Hampson
Paul "TBBle" Hampson
Compared to January, I've identified and have a fix for the issue that https://github.com/microsoft/hcsshim/pull/901 shows on Windows 10 20H2, but that PR is still pending merge, and then the fix...
One kind-of heavy-weight option, used by ue4-docker, is running a service outside the container that exposes the secret, and have the container image build pull that secret over the network...
The mixed protocols in one service [KEP](https://github.com/kubernetes/enhancements/pull/1438) isn't in 1.19 currently, as there seems to be some pending decisions about how to handle the feature introduction and what happens when...
Support for this would come via https://github.com/kubernetes-sigs/aws-load-balancer-controller/issues/1608.
Hmm. At a quick guess, the BuildKit-internal HTTP code is not seeing the proxy config; it _should_ be pulling it from the environment from a brief skim of the code,...
As a workaround, you might be able to use an externally-managed TCP_UDP LB and bind it to a non-LB Service, see https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/guide/use_cases/self_managed_lb/ and https://kubernetes-sigs.github.io/aws-load-balancer-controller/v2.4/guide/targetgroupbinding/targetgroupbinding/. The same suggestion was made in...
/remove-lifecycle stale
Those errors came from containerd, and look like they would have been part of the `pull` call, not the `run` call. I guess that layer contained both `pam.7.gz` and `PAM.7.gz`...
If this is related to Access Denied errors when Docker tries to remove an unused layer, it might be another manifestation of https://github.com/microsoft/Windows-Containers/issues/358, in which case it's an OS-level issue...
As described in the linked comment, this change makes sense to me, although I haven't reviewed the patch. As noted, this was on my list of "hacked around and will...