© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
@Alex: nope, in my case, the "old" container was running as expected. Proof: keystone port was already occupied, preventing the keystone-<blah> to start and use that very same port.