Any benefit to switching to docker machine for swarm initialisation? #16
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#16
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
It looks like
docker-machine
has ageneric
driver which connects over SSH, and handles installing certificates for remote connections for you:https://www.linux.com/topic/cloud/how-use-docker-machine-create-swarm-cluster/
I'm wondering if that's easier than my other ideas for #12, which were:
abra
command to initialse swarm, have a--server
mode to the abra installer scriptHoly cow, that machine project looks sick. Just saw this now too https://github.com/JonasProgrammer/docker-machine-driver-hetzner. Pretty handy. Definitely up for trying to see how it handles the certificates!
It looks like Docker machine was "superseded" in favour of infrakit / deploykit, which is now itself deprecated (a likely-sounding corporate bullshit conspiracy explanation is ventured in first link..)
There's a somewhat-active
machine
fork here: https://github.com/machine-drivers/machineOne suggestion from the "superseded" thread was to use
export DOCKER_HOST=ssh://root@example.com
, I'm giving that a go now.Requires user to be in the
docker
group.Certificate set-up was my main draw to
docker-machine
; I'll close this for now and we can reopen it if it still seems like a good option for the server set-up side.As of
abra/f4798bf
: