-
Notifications
You must be signed in to change notification settings - Fork 2k
Importing existing machines #1229
Comments
Hm, there is the The one caveat is that if I am not mistaken, there is not complex support for cert generation + management with that right now, so it will generate the certs and store them locally on wherever you run the If you have ideas / suggestions on how you'd prefer to see this work, we're highly open to it :) Trying to figure this type of scenario / sharing machines on teams etc. I think will be very important for next steps. |
My particular use-case is the former where I have Docker machines already running but were not created/managed with |
I think if you've provisioned the docker hosts with some other method, you could also create certificates manually for the server & clients from a new or existing company CA following https://docs.docker.com/articles/https/. Then I'd like some improvements to how machine treats partial but sensible certificate file presence in #1233 to let us still use docker machine in this situation. The generic driver will I suspect still over-validate the certificate files present, somewhere inside getMachineConfig(). I suspect all the entries in config.json aren't being actually used, only the machineDir... |
What I'd ideally like to see is the |
That sounds like what I think "generic" might do (if it might also re-install docker), but to be clear that's not what I'm after in #1233 - which is just the client side pointer to a correctly setup docker. I want what I do as I don't see how docker-machine can do the correct creation/distribution of SSL certs for multiple users/hosts according to arbitrary internal company security standards, as @nathanleclaire suggests. |
Oh yes, this is exactly what |
Oh!? I'll have to try it out on master then :) I'll see how it all works out :) |
+1 on "create -d generic" I had a set of n machines running docker engine but not configured properly Please note that "docker-machine create -d generic" will reboot your This was great because I didn't want to follow all the manual steps to On Wed, May 27, 2015 at 4:08 AM, James Mills notifications@github.com
|
@ljrittle thanks for the feedback! I had not thought of using |
This basically doesn't work for me; See below:
|
@prologic - looks like your SSH key is password-protected, so |
Perhaps this is a bug? I'll try but most of my access keys (separate to m2m keys0 are passpharse protected. |
Cool no worries; I'll test with a passpharseless key |
Definitely would like to support passphrase SSH key usage. I've filed an issue here: #1473 |
👍 |
The docker-machine create solution, with a generic driver allowed me to import an existing docker-machine into my computer, but the fact that the certificates were regenerated, it meant that it stopped working on the machine where it was created originally.
What worked for me, was to copy the folders under ~/.docker/machine/ to my local machine. Then I had to amend the paths on config.json, as in my case they were different. |
Scenario: We have several or more Docker Hosts setup on various cloud providers already running some form of Linux+Docker; e.g: Digital Ocean + Ubuntu 14.04 + Docker
Is there currently a good way to "import" these hsots into docker-machine controlled states for future management without having to destroy them and re-create fresh new ones?
The text was updated successfully, but these errors were encountered: