vfarcic / docker-flow

Docker Flow: Walkthrough

Deprecated

Since the emergence of Docker Swarm Mode, this project is deprecated. If you're interested in tools that can help you orchestrate a Swarm cluster, please visit the Docker Flow Proxy project.

docker-flow's Issues

Program exits without a warning when CONSUL_IP is not provided

Swarm Mode in 1.12

The swarm mode seems to have left out external service discovery. Will this be the preferred way to configure Docker Flow in production?

Another implementation

Hello,

I have see this another implementation to rolling-upgrade:
https://github.com/rancher/rancher-compose/blob/master/upgrade/upgrade.go

This is a good job and i'm very interestion with this feature for production soon

Provide docker-flow inside a container

Strategy to handle Docker images with blue/green deployment

Docker Swarm requires that Docker image for the application/service is pushed to a private registry prior to deployment. If I remember right, local image can be deployed to Swarm but rescheduling to another node will fail...? In blue/green deployment scenario, failed deployment would require also Docker images to be rolled back from registry. Better yet, if the revision of the image would not be at hands of users before deployment is verified. How to handle such failure scenario in terms of Docker images?

HAProxy templates

Hi.

I'd like to be able to use a specific HAProxy template to be dynamically updated in a similar way to consul-template.
That is I need to have multiple backends, each of which are updated for a specific service.

Is there any way of doing that right now?

Support for multiple Docker compose files

Sometimes multiple Docker compose files form a hierarchy to avoid duplication as described here https://docs.docker.com/compose/extends/

We for example have

• docker-compose.yml
• docker-compose.override.yml
• docker-compose-ci.yml
• docker-compose-deploy.yml

First two are used when running the application locally. Files contain sensible default configuration (for example ports or application properties) and contain no variables to substitute. The last two files serve special purposes in the CD pipeline and either add, override or use the configuration from the first file.

Application is deployed to Swarm with command:
docker-compose -f docker-compose.yml -f docker-compose-deploy.yml up -d

Locally you can just run:
docker-compose up -d

Use generic driver, instead of virtual box to install docker swarm

Hi all,

I try to build a docker-machine with swarm using generic driver, it failed. Here is the error message. Have you met it before?

docker-machine create -d generic --generic-ip-address 10.0.0.246 --generic-ssh-key $HOME/.ssh/id_rsa --generic-ssh-user patrick --generic-ssh-port 22 --swarm --swarm-master --swarm-discovery="consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-store=consul://$(docker-machine ip consul-machine):8500" --engine-opt="cluster-advertise=eth1:2376" swarm-master

Here is the error message.
Running pre-create checks...
Creating machine...
(swarm-master) Importing SSH key...
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(systemd)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring swarm...
Error creating machine: Error running provisioning: Unable to pull image: Post https://10.0.0.246:2376/v1.15/images/create?fromImage=swarm%3Alatest: read tcp 10.0.0.113:52811->10.0.0.246:2376: read: connection reset by peer

trying to use generic driver, instead of virtualbox

When trying to build a docker-machine using generic driver, it failed. Running on a MacOS 10:10:5, connecting to a clean version of Ubuntu 14.04. Docker log from remote machine attached /var/log/upstart/docker.log
docker.txt

Any clues? Thanks, frank [email protected]
Here is the terminal view:

frankscaffasmbp:docker-flow frankschaffa$ docker-machine create \

--driver generic
--generic-ip-address=9.12.235.184
--generic-ssh-user=root
--swarm --swarm-master
--swarm-discovery="consul://9.12.247.254:8500"
--engine-opt="cluster-store=consul://9.12.247.254:8500"
--engine-opt="cluster-advertise=eth1:2376"
swarm-master
Running pre-create checks...
Creating machine...
(swarm-master) No SSH key specified. Connecting to this machine now and in the future will require the ssh agent to contain the appropriate key.
Waiting for machine to be running, this may take a few minutes...
Detecting operating system of created instance...
Waiting for SSH to be available...
Detecting the provisioner...
Provisioning with ubuntu(upstart)...
Installing Docker...
Copying certs to the local machine directory...
Copying certs to the remote machine...
Setting Docker configuration on the remote daemon...
Configuring swarm...
Error creating machine: Error running provisioning: Unable to pull image: Post https://9.12.235.184:2376/v1.15/images/create?fromImage=swarm%3Alatest: dial tcp 9.12.235.184:2376: getsockopt: connection refused
frankscaffasmbp:docker-flow frankschaffa$