mesos-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Tobias Pfeiffer (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (MESOS-6183) mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images
Date Wed, 02 Nov 2016 06:23:59 GMT

    [ https://issues.apache.org/jira/browse/MESOS-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15627924#comment-15627924
] 

Tobias Pfeiffer commented on MESOS-6183:
----------------------------------------

My understanding of this issue is the following: When I set up a private registry without
an HTTPS certificate, then I need to add the {{--insecure-registry hostname:5000}} parameter
to all Docker daemons that are supposed to fetch from this registry. Now with the Docker containerizer,
this works fine, specifying {{mydockerreg:5000/image:tag}} as an image will correctly download
that image and run it. With the Mesos containerizer, this fails with

bq.  Failed to launch container: Failed to perform 'curl': curl: (35) error:140770FC:SSL routines:SSL23_GET_SERVER_HELLO:unknown
protocol

I assume that internally curl gets a URL like https://mydockerreg:5000/... and therefore attempts
an SSL handshake. It should instead offer a way to specify that this should be a non-SSL connection.

> mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images
> ---------------------------------------------------------------------------------------
>
>                 Key: MESOS-6183
>                 URL: https://issues.apache.org/jira/browse/MESOS-6183
>             Project: Mesos
>          Issue Type: Bug
>            Reporter: yongyu
>            Priority: Minor
>
> mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message