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.

Sign up for GitHub

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

Jump to bottom

Can (seemingly) deploy containers on deactivated hosts #100

Closed
feliksik opened this issue Feb 13, 2015 · 2 comments · May be fixed by rancherfederal/carbide-docs#101
Closed

Can (seemingly) deploy containers on deactivated hosts #100

feliksik opened this issue Feb 13, 2015 · 2 comments · May be fixed by rancherfederal/carbide-docs#101

Comments

@feliksik
Copy link

I accidentally deactivated a host (misclicked, and didn't even realize it - warning 1).

Warning 2 is that I then tried to deploy docker containers. After setting up the container name, port forwarding etc. I clicked create, and nothing happened. Confused!

A simple solution would be to to disallow container creation when a host is deactivated.
@hibooboo2
Copy link

This Is no longer an issue with the latest version. Hosts now lose the add container when they are inactive.

@vincent99
Copy link
Contributor

Fixed in rancher/ui#64

JeffersonBledsoe pushed a commit to JeffersonBledsoe/rancher-cli that referenced this issue Apr 28, 2022
Merge pull request rancher#100 from carolynhu/prunev2
4416a61 
rancher-compose-executor v0.14.21
@atoy3731 atoy3731 mentioned this issue Jul 19, 2024
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Classified Provisioning Docs rancherfederal/carbide-docs
3 participants
@vincent99 @hibooboo2 @feliksik