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

Detect other container management tools running instances #1081

Open
1 task done
evertonlperes opened this issue Dec 7, 2021 · 0 comments
Open
1 task done

Detect other container management tools running instances #1081

evertonlperes opened this issue Dec 7, 2021 · 0 comments
Labels
kind/enhancement New feature or request
Projects

Comments

@evertonlperes
Copy link
Contributor

Preflight Checklist

  • I have searched the issue tracker for a feature request that matches the one I want to file, without success.

Problem Description

Rancher Desktop does not detect other container management tools instances on the environment.

Test scenario:

  • Open RD and wait until it be loaded
  • Open another container management tool and wait until it be loaded
    Result: The second container management tool will overwrite the RD socket config.

Proposed Solution

  • Create a feature to detect/inform if there's other container management tools are running along RD.
  • Modal to inform user that Rancher cannot work along with other container management tools.
  • Nice to have: If there's another instance, ask user to choose which one should be running and close the others.

Additional Information

No response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/enhancement New feature or request
Projects
No open projects
Stripey
To do
Development

No branches or pull requests

1 participant