Skip to content
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

Continuous deployment step #15

Open
ilan-schemoul opened this issue Feb 4, 2020 · 0 comments
Open

Continuous deployment step #15

ilan-schemoul opened this issue Feb 4, 2020 · 0 comments

Comments

@ilan-schemoul
Copy link

ilan-schemoul commented Feb 4, 2020

I think the important part (that I've been struggling on for few weeks) is CONTINUOUS Deployment, it's not entirely shown here.
For me it would be after PUSHING to docker hub, to use docker-machine to create a machine with ssh driver, then docker stack deploy.
Unfortunately docker stack deploy I use in my step does NOT seem to use the dockercfg despite I put the dockercfg in steps and services !
command: /bin/bash -c "echo -e $PRIVATE_SSH_KEY > /root/.ssh/id_rsa && chmod 600 /root/.ssh/id_rsa && chmod +x /opt/app/create-manager-machine.sh && cd /opt/app && sh /opt/app/create-manager-machine.sh"
with create-manager-machine.sh being #!/bin/sh docker-machine create --driver generic --generic-ip-address=198.211.127.192 --generic-ssh-key ~/.ssh/id_rsa worksheets-v2 docker-machine ssh worksheets-v2 "docker swarm init --advertise-addr=198.211.127.192" eval "$(docker-machine env worksheets-v2 --shell sh)" docker stack deploy --compose-file devops/docker-compose-prod.yml webapp --with-registry-auth gives image nitrobay/worksheets_v2:latest could not be accessed on a registry to record
its digest. Each node will access nitrobay/worksheets_v2:latest independently,
Proving that docker stack deploy does not use dockercfg

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant