Repository navigation
make it obvious in terminal for user if using docker-env #6489
Description
I was thinking as part of the eval $(minikube docker-env) we could pass something that changes the terminal Prompt so it is obvious for the user they are usinf minikube's docker not their own docker.
maybe:
something like:
medya@~ $ PS1="$PS1""(using minikube dockerd) $:"
that will try turn into
medya@~ $ (using minikube dockerd) $:
the minikube word would be profile name, this will also make it clear which profile's docker-env we are using.
helps with #6462
helps with #6437
also we could explicity set a ENV that says
USES_MINIKUBE_DOCKERD=PROFILE_NAME
Metadata
Metadata
Assignees
Labels
docker-env issuesDenotes an issue ready for a new contributor, according to the "help wanted" guidelines.Categorizes issue or PR as related to documentation.Categorizes issue or PR as related to a new feature.Indicates that an issue or PR should not be auto-closed due to staleness.Higher priority than priority/awaiting-more-evidence.
Activity
[-]make it obvious for user if using docker-env[/-][+]make it obvious in terminal for user if using docker-env[/+]tstromberg commentedon Feb 4, 2020
Environment variable sounds good.
I wouldn't be opposed to prompt manipulation if it was an extra flag to docker-env. Like
minikube docker-env --prompt. I would prefer it be explicit, as not everyone is going to like us manipulating their prompt.Keep in mind that many folks build prompts with dynamic functions, particularly in the zsh and fish community.
afbjorklund commentedon Mar 7, 2020
This sounds like something that should be a part of docker, rather than minikube ?
i.e. displaying the DOCKER_HOST in the prompt
We don't even put the current kubectl context in the prompt, which sounds more related.
Like in https://github.com/jonmosco/kube-ps1
afbjorklund commentedon Mar 15, 2020
I guess this is now implemented, with MINIKUBE_ACTIVE_DOCKERD ?
What needs to be done is a shell function to use it, similar to:
https://gist.github.com/aburnett/1165239cd2673a43579c
Then the user can use that in their PS1, similar to e.g. __git_ps1
https://github.com/git/git/blob/master/contrib/completion/git-prompt.sh
One thing that is weird is that it shows the name of the profile (not host) ?
fejta-bot commentedon Jun 16, 2020
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-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale
fejta-bot commentedon Jul 16, 2020
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-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten
19 remaining items
JacekDuszenko commentedon Jun 3, 2021
I'd happily add the tutorial.
@medyagh which place in the docs would be the best to put it in? Could you post a link? Thanks
spowelljr commentedon Jun 23, 2021
@JacekDuszenko We have a tutorial section on the minikube website here: https://minikube.sigs.k8s.io/docs/tutorials/
JacekDuszenko commentedon Jun 23, 2021
Cool, I'll add it there then /assign @JacekDuszenko
JacekDuszenko commentedon Jun 23, 2021
/assign @JacekDuszenko
k8s-triage-robot commentedon Sep 21, 2021
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:
lifecycle/staleis appliedlifecycle/stalewas applied,lifecycle/rottenis appliedlifecycle/rottenwas applied, the issue is closedYou can:
/remove-lifecycle stale/lifecycle rotten/closePlease send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
spowelljr commentedon Sep 21, 2021
@JacekDuszenko Are you still working on this?
Rushali-Sarkar commentedon Dec 17, 2025
Hi, is this issue still open ? Can I take this up as my first issue ?
BlackBuck commentedon Jan 27, 2026
Hi, @medyagh @JacekDuszenko
anyone working on this issue currently? Would be happy to help!
iacker commentedon Apr 7, 2026
I am working on a docs PR for this issue, focused on adding a small tutorial/tip to the minikube website around using
MINIKUBE_ACTIVE_DOCKERDin the shell prompt, based on the guidance already discussed here. /assignChampbreed commentedon Aug 21, 2026
/Assign