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

triton-compose should support newer docker-compose #17

Open
jussisallinen opened this Issue Oct 5, 2017 · 5 comments

Comments

Projects
None yet
4 participants
@jussisallinen

jussisallinen commented Oct 5, 2017

Current version of triton-compose (docker-compose version 1.9.0, build 2585387) doesn't work well with LetsEncrypt (triton-dehydrated) certificates on OS X:

$ triton-compose ps
ERROR: SSL error: [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:590)

Newer docker-compose (docker-compose version 1.16.1, build 6d1ac21) works with LetsEncrypt certificates but image pull operations fail on Triton side:

latest: Pulling from autopilotpattern/vault (req afa6d532-a815-4d24-bb80-7882ac3b83d5)
ERROR: Error pulling image: Internal error (afa6d532-a815-4d24-bb80-7882ac3b83d5)

Task Summary on AdminUI shows:

pull_image_v2_layers
pullImageLayers failed - no successful create-docker-image
@jussisallinen

This comment has been minimized.

Show comment
Hide comment
@jussisallinen

jussisallinen Oct 9, 2017

To be exact atleast Brew docker-compose 1.16.1 doesn’t give the SSL error if that helps.

jussisallinen commented Oct 9, 2017

To be exact atleast Brew docker-compose 1.16.1 doesn’t give the SSL error if that helps.

@jussisallinen

This comment has been minimized.

Show comment
Hide comment
@jussisallinen

jussisallinen Oct 9, 2017

Turned out fix for the certificate error was as easy as downloading newer cacert.pem from https://curl.haxx.se/docs/caextract.html
and doing export CURL_CA_BUNDLE=cacert.pem

jussisallinen commented Oct 9, 2017

Turned out fix for the certificate error was as easy as downloading newer cacert.pem from https://curl.haxx.se/docs/caextract.html
and doing export CURL_CA_BUNDLE=cacert.pem

@liftedkilt

This comment has been minimized.

Show comment
Hide comment
@liftedkilt

liftedkilt Oct 12, 2017

@jussisallinen - thanks for the workaround. That is very helpful.

liftedkilt commented Oct 12, 2017

@jussisallinen - thanks for the workaround. That is very helpful.

@alaslums

This comment has been minimized.

Show comment
Hide comment
@alaslums

alaslums May 10, 2018

+1 having this issue - would be nice if it was fixed officially

alaslums commented May 10, 2018

+1 having this issue - would be nice if it was fixed officially

@Teutone

This comment has been minimized.

Show comment
Hide comment
@Teutone

Teutone May 18, 2018

Happened here too. Workaround confirmed working. Thanks!

Teutone commented May 18, 2018

Happened here too. Workaround confirmed working. Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment