Skip to content
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

Closed
anjannath opened this issue Feb 7, 2024 · 0 comments · Fixed by #4025
Closed

crc oc-env adds podman client to path #4022

anjannath opened this issue Feb 7, 2024 · 0 comments · Fixed by #4025
Assignees
Labels
kind/bug Something isn't working

Comments

@anjannath
Copy link
Member

When running crc oc-env users would expect to only have oc setup to use the CRC cluster, and when user wants to use podman from crc, running crc podman-env would to set it up.

% crc status
CRC VM:          Running
MicroShift:      Running (v4.14.8)
RAM Usage:       1.204GB of 16.01GB
Disk Usage:      4.993GB of 16.1GB (Inside the CRC VM)
Cache Usage:     255GB
Cache Directory: /Users/anath/.crc/cache

% which podman
/opt/podman/bin/podman

% eval `crc oc-env`

% which podman
/home/anath/.crc/bin/oc/podman

this happens because currently both oc and podman binaries are in the same dir ~/.crc/bin/oc, and eval 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 to PATH when crc podman-env is ran

@anjannath anjannath added the kind/bug Something isn't working label Feb 7, 2024
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 anjannath moved this from Todo to Ready for review in Project planning: crc Feb 14, 2024
@anjannath anjannath self-assigned this Feb 20, 2024
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 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
Labels
kind/bug Something isn't working
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

1 participant