Skip to content
This repository was archived by the owner on May 9, 2022. It is now read-only.

Support boot2docker (and its tcp + ssl thing)#5

Merged
spraints merged 4 commits into
github:masterfrom
spraints:boot2docker-tls
Jun 19, 2015
Merged

Support boot2docker (and its tcp + ssl thing)#5
spraints merged 4 commits into
github:masterfrom
spraints:boot2docker-tls

Conversation

@spraints
Copy link
Copy Markdown
Contributor

This branch makes it so that hoosegow can use the environment variables set by boot2docker shellinit. It does this by not setting Docker.url if no connection parameters are provided. This lets the docker-api gem figure out where to connect, which should be right most of the time. This branch also bumps the docker-api gem version: 1.15 is where it learned to use boot2docker over TLS (upserve/docker-api#210), and 1.19 has a fix for attached containers (upserve/docker-api#251).

cc @mastahyeti

spraints added 4 commits June 16, 2015 16:11
boot2docker sets env vars like this:

    export DOCKER_HOST=tcp://192.168.59.104:2376
    export DOCKER_CERT_PATH=/Users/spraints/.boot2docker/certs/porter
    export DOCKER_TLS_VERIFY=1

The docker-api gem initializes `Docker.url` from these variables. If
boot2docker and docker-api already know what the docker connection is,
we don't need to mess with it in hoosegow.
This is when docker-api learned about the `DOCKER_*` environment
variables.
@btoews
Copy link
Copy Markdown
Contributor

btoews commented Jun 18, 2015

👍

spraints added a commit that referenced this pull request Jun 19, 2015
Support boot2docker (and its tcp + ssl thing)
@spraints spraints merged commit 4c61c96 into github:master Jun 19, 2015
@spraints spraints deleted the boot2docker-tls branch June 19, 2015 22:45
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants