-
Notifications
You must be signed in to change notification settings - Fork 54
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
Push upstream into docker machine #29
Comments
While it would be cool to see this project make it into upstream docker, I'm not sure we really qualify for official inclusion. We don't have tests at all and the code is mostly undocumented. Granted, the logic is not very complex, but I doubt the docker people would want something like this in their codebase. Currently I don't have time to get this into an includable state. Perhaps that's something for the semester vacation... This aspect aside, it actually takes ages to get something accepted into docker. Just listing our driver took more than half a year (see #7). So even if we decide to get this into a state that might be included, you guys shouldn't hold your breath to list hetzner cloud as docker-native any time soon ;) |
I would just go for adding some of our documentation to the official one. Linode for example does this, the driver of them is located in their own repository but the documentation is i the official docs. Or just at least some backlinks. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Anyways, isn't the docker-machine repo in maintenance-only mode? |
Good catch. Let's close this one. Ref: docker/machine#4537 |
Hello guys,
what would you think about pushing this machine driver to docker machine directly so it is "built-in"? https://github.com/docker/machine/tree/master/drivers
Pro: Users won't need to download the driver on there own
Pro: This would be an official docker driver
Pro: Documentation would be available in the Docker docs.
The text was updated successfully, but these errors were encountered: