-
Notifications
You must be signed in to change notification settings - Fork 242
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.
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
crc oc-env
adds podman
client to path
#4022
Labels
kind/bug
Something isn't working
Comments
anjannath
added a commit
to anjannath/crc
that referenced
this issue
Feb 8, 2024
earlier both oc and podman binaries were present in the ~/.crc/bin/oc dir and added to PATH by the `crc oc-env` command, which resulted in adding both the binaries to path when the user might want only the `oc` binary to be added to path by the `crc oc-env` command this adds the `podman` binary in a separate directory ~/.crc/bin/podman and is added to PATH by running the `crc podman-env` command fixes crc-org#4022
anjannath
added a commit
to anjannath/crc
that referenced
this issue
Feb 8, 2024
earlier both oc and podman binaries were present in the ~/.crc/bin/oc dir and added to PATH by the `crc oc-env` command, which resulted in adding both the binaries to path when the user might want only the `oc` binary to be added to path by the `crc oc-env` command this adds the `podman` binary in a separate directory ~/.crc/bin/podman and is added to PATH by running the `crc podman-env` command fixes crc-org#4022
anjannath
added a commit
to anjannath/crc
that referenced
this issue
Feb 8, 2024
earlier both oc and podman binaries were present in the ~/.crc/bin/oc dir and added to PATH by the `crc oc-env` command, which resulted in adding both the binaries to path when the user might want only the `oc` binary to be added to path by the `crc oc-env` command this adds the `podman` binary in a separate directory ~/.crc/bin/podman and is added to PATH by running the `crc podman-env` command fixes crc-org#4022
anjannath
added a commit
to anjannath/crc
that referenced
this issue
Feb 8, 2024
earlier both oc and podman binaries were present in the ~/.crc/bin/oc dir and added to PATH by the `crc oc-env` command, which resulted in adding both the binaries to path when the user might want only the `oc` binary to be added to path by the `crc oc-env` command this adds the `podman` binary in a separate directory ~/.crc/bin/podman and is added to PATH by running the `crc podman-env` command fixes crc-org#4022
anjannath
added a commit
to anjannath/crc
that referenced
this issue
Feb 8, 2024
earlier both oc and podman binaries were present in the ~/.crc/bin/oc dir and added to PATH by the `crc oc-env` command, which resulted in adding both the binaries to path when the user might want only the `oc` binary to be added to path by the `crc oc-env` command this adds the `podman` binary in a separate directory ~/.crc/bin/podman and is added to PATH by running the `crc podman-env` command fixes crc-org#4022
anjannath
added a commit
to anjannath/crc
that referenced
this issue
Feb 21, 2024
earlier both oc and podman binaries were present in the ~/.crc/bin/oc dir and added to PATH by the `crc oc-env` command, which resulted in adding both the binaries to path when the user might want only the `oc` binary to be added to path by the `crc oc-env` command this adds the `podman` binary in a separate directory ~/.crc/bin/podman and is added to PATH by running the `crc podman-env` command fixes crc-org#4022
praveenkumar
pushed a commit
that referenced
this issue
Mar 8, 2024
earlier both oc and podman binaries were present in the ~/.crc/bin/oc dir and added to PATH by the `crc oc-env` command, which resulted in adding both the binaries to path when the user might want only the `oc` binary to be added to path by the `crc oc-env` command this adds the `podman` binary in a separate directory ~/.crc/bin/podman and is added to PATH by running the `crc podman-env` command fixes #4022
github-project-automation
bot
moved this from Ready for review
to Done
in Project planning: crc
Mar 8, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
When running
crc oc-env
users would expect to only haveoc
setup to use the CRC cluster, and when user wants to usepodman
from crc, runningcrc podman-env
would to set it up.this happens because currently both
oc
andpodman
binaries are in the same dir~/.crc/bin/oc
, andeval crc-env
adds the~/.crc/bin/oc
dir to PATH.we could instead create a separate dir for podman
~/.crc/bin/podman
and add this dir toPATH
whencrc podman-env
is ranThe text was updated successfully, but these errors were encountered: