Using a proxy with containerd runtime

[dkadetov]

Now I use the default container runtime (docker) in minikube. And at the start, I specify the option to use a proxy:

minikube start --docker-env HTTP_PROXY=<my proxy>

But what about using containerd? How can I specify the environment setting in this case?

minikube start --container-runtime=containerd

In production we are already using a containerd. Therefore, I need to use it in minikube too.
I only found solution when it is used without minikube.

[afbjorklund]

We need to make the docker-env more generic, and use something like --runtime-env and --runtime-opt

      --docker-env=[]: Environment variables to pass to the Docker daemon. (format: key=value) DEPRECATED
      --docker-opt=[]: Specify arbitrary flags to pass to the Docker daemon. (format: key=value) DEPRECATED

      --runtime-env=[]: Environment variables to pass to the container runtime. (format: key=value)
      --runtime-opt=[]: Specify arbitrary flags to pass to the container runtime. (format: key=value)

For now, you will have to edit the configuration using minikube ssh (or from the bootup script perhaps)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten