Skip to content

docs: add docker-env prompt tip #22808

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
iacker wants to merge 1 commit into
base: master
Choose a base branch
from
+20 −0
Open

docs: add docker-env prompt tip #22808

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
20 changes: 20 additions & 0 deletions site/content/en/docs/handbook/pushing.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -107,9 +107,29 @@ By closing the terminal, you will go back to using your own system's docker daem

{{% pageinfo color="info" %}}
Tip 3:
You can use the `MINIKUBE_ACTIVE_DOCKERD` environment variable in your shell prompt to remind yourself when `docker` commands are targeting the Docker daemon inside minikube.

For example, in `bash` or `zsh`:

```shell
__active_minikube() {
if [ -n "$MINIKUBE_ACTIVE_DOCKERD" ]; then
printf ' minikube (%s)' "$MINIKUBE_ACTIVE_DOCKERD"
fi
}

export PS1='\\u@\\h:\\w$(__active_minikube)\\$ '
```

When you run `eval $(minikube docker-env)`, the prompt will show the active minikube profile name. If you already use a custom prompt, adapt the example instead of replacing your prompt configuration verbatim.
{{% /pageinfo %}}

{{% pageinfo color="info" %}}
Tip 4:
In container-based drivers such as Docker or Podman, you will need to re-do docker-env each time you restart your minikube cluster.
{{% /pageinfo %}}


More information on [docker-env](https://minikube.sigs.k8s.io/docs/commands/docker-env/)

---
Expand Down