https://pulumi.com
Join Slack
This message was deleted.
# getting-started
s
This message was deleted.
s
If you can find an AMI that has a sufficiently recent enough version of Docker pre-installed, then you could instantiate some number of EC2 instances using that AMI and then use the 
Command
module to run the Docker commands necessary to establish a Swarm cluster.
b
how do i get return from 
docker swarm init
, which is needed for the worker nodes?
s
If you’re using 
command.remote.Command
(see https://www.pulumi.com/registry/packages/command/api-docs/remote/command/) there are 
stdout
and 
stderr
outputs that should capture the return of the 
docker swarm init
command. You’ll have to parse it down to what you need, and then pass that information on to create the worker nodes.
BTW, the reason I suggested the 
Command
module is because the current Docker provider does not have any functionality for establishing a Swarm cluster.
b
got you, thanks
I checked the command module, it needs direct ssh access. Usually I setup worker er2 instances to have only private ip addresses. Any suggestion? @salmon-account-74572
s
Use an SSH bastion?
b
I don't see how to set up bastion host in command module.
the manager node has public ip, can be the jump host, in my setup
s
Sorry---bastion host (or jump host) isn’t part of the Command module, Using a node with a public IP, as you’ve suggested, is what I meant. Apologies that I wasn’t more clear.
b
trying to work around this issue now
thanks
32 Views
Open in Slack
PreviousNext
Powered by

Pulumi Community

No matter how you like to participate in developer communities, Pulumi wants to meet you there. If you want to meet other Pulumi users to share use-cases and best practices, contribute code or documentation, see us at an event, or just tell a story about something cool you did with Pulumi, you are part of our community.

Powered by