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

Account for Differing CloudAPI/Docker Endpoints #30

Open
qdzlug opened this issue Dec 14, 2017 · 0 comments
Open

Account for Differing CloudAPI/Docker Endpoints #30

qdzlug opened this issue Dec 14, 2017 · 0 comments

Comments

@qdzlug
Copy link

qdzlug commented Dec 14, 2017

Hi,

I'm going to throw a PR together for this, but wanted to log it. The Triton setup script assumes a certain API endpoint format (with datacenter at the beginning of the URL), which may not be the case for many non-Joyent datacenters.

For example:

$ ./setup.sh

Error! The Triton CLI configuration does not match the Docker CLI configuration.

Docker user: jay.schmidt
Triton user: jay.schmidt
Docker data center: docker
Triton data center: cloudapi

With a config of:

$ env | grep DOCKER
DOCKER_CLIENT_TIMEOUT=300
DOCKER_CERT_PATH=/Users/jschmidt/.sdc/docker/cak1-jay.schmidt
DOCKER_HOST=tcp://docker.cak-1.virington.com:2376
DOCKER_TLS_VERIFY=1
$ env | egrep "SDC|TRITON"
SDC_KEY_ID=6b:95:03:3d:d3:6e:52:69:01:96:1a:46:4a:8d:c1:7e
SDC_ACCOUNT=jay.schmidt
SDC_URL=https://cloudapi.cak-1.virington.com

In my case, the DC is the secondary item in the URL (due to using CMON). One possible fix is to just have a flag to ignore this check; a second fix is to actually query cloudapi/docker to check the datacenter. I'll work on this later this month.

Jay

@qdzlug qdzlug changed the title Account for Differening CloudAPI/Docker Endpoints Account for Differing CloudAPI/Docker Endpoints Dec 14, 2017
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