You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I started Podman Desktop, and the sandbox instance I was using yesterday has 'unknown' status. Ok, no problem, it must just be logged out. But to log in again I had to:
Find sandbox website
Login to RedHat
Navigate through 3 or 4 pages to get to oc login command
Open terminal
Execute oc login
... which created a new context instead of using the one I had created yesterday. I can set this context inside of Podman Desktop using the system tray, but my Sandbox instance still says 'unknown'. I can't edit the instance to change the context; I can't create a new instance with the new context b/c it already exists. The only way to show the sandbox connection as running again is to create a new instance with a third context.
It's painful to have to go to the sandbox repeatedly to get the (re-)login command; this should be possible within PD.
I should be able to continue using one Sandbox instance indefinitely.
The text was updated successfully, but these errors were encountered:
Having a default (non-conflicting) name as per #20 would be great and help with usability, but wouldn't solve this problem where I continually need to create new instances and delete old ones.
I started Podman Desktop, and the sandbox instance I was using yesterday has 'unknown' status. Ok, no problem, it must just be logged out. But to log in again I had to:
oc login
command... which created a new context instead of using the one I had created yesterday. I can set this context inside of Podman Desktop using the system tray, but my Sandbox instance still says 'unknown'. I can't edit the instance to change the context; I can't create a new instance with the new context b/c it already exists. The only way to show the sandbox connection as running again is to create a new instance with a third context.
The text was updated successfully, but these errors were encountered: