Corporate firewall issues

[marcelned]

Our corporate firewall only allows access to dockerhub.

I have tried the standard gcr as well as the chinese alternative.

🔥  Creating podman container (CPUs=2, Memory=292500MB) ...
🤦  StartHost failed, but will try again: creating host: create: creating: setting up container node: preparing volume for minikube container: sudo -n podman run --rm --name minikube-preload-sidecar --label created_by.minikube.sigs.k8s.io=true --label name.minikube.sigs.k8s.io=minikube --entrypoint /usr/bin/test -v minikube:/var gcr.io/k8s-minikube/kicbase:v0.0.26 -d /var/lib: exit status 125
stdout:

stderr:
Trying to pull gcr.io/k8s-minikube/kicbase:v0.0.26...
  Get "https://gcr.io/v2/": dial tcp 173.194.76.82:443: i/o timeout
Error: Error initializing source docker://gcr.io/k8s-minikube/kicbase:v0.0.26: error pinging docker registry gcr.io: Get "https://gcr.io/v2/": dial tcp 173.194.76.82:443: i/o timeout

any chance the PowerPC images can be uploaded to dockerhub?

[sharifelgamal]

Unfortunately, we don't currently build the base image for the docker/podman driver for power pc just yet, but it is a work in progress. See #12399 for more details on that.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[spowelljr]

We have a kicbase image for ppc64le as of v1.25.0