[jira] [Commented] (MESOS-6183) mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images
[ https://issues.apache.org/jira/browse/MESOS-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880894#comment-16880894 ] longfei commented on MESOS-6183: [https://reviews.apache.org/r/71024/] > 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 >Assignee: longfei >Priority: Minor > > mesos's Unified Containerizer cannot set "--insecure-registry" when > provisioning images -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-6183) mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images
[ https://issues.apache.org/jira/browse/MESOS-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880401#comment-16880401 ] longfei commented on MESOS-6183: I added a new flag --insecure_docker_registry. The rule is that only one of --docker_registry and --insecure_docker_registry can be used. The default value of --docker_registry([https://registry-1.docker.io)|https://registry-1.docker.io%29/] is removed because it will always be set if not specified in the slave's command, which will not respect the rule above. > 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 >Assignee: longfei >Priority: Minor > > mesos's Unified Containerizer cannot set "--insecure-registry" when > provisioning images -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MESOS-6183) mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images
[ https://issues.apache.org/jira/browse/MESOS-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16880338#comment-16880338 ] longfei commented on MESOS-6183: Hello. I also ran into this issue recently. And I have modified slave's code a little bit. [~jieyu], [~kaysoky], [~gilbert], would you shepherd this please? > 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 (v7.6.3#76005)
[jira] [Commented] (MESOS-6183) mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images
[
https://issues.apache.org/jira/browse/MESOS-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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)
[jira] [Commented] (MESOS-6183) mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images
[ https://issues.apache.org/jira/browse/MESOS-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15523748#comment-15523748 ] Joseph Wu commented on MESOS-6183: -- Closing this issue due to lack of information to see what the request/problem is. > 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)
[jira] [Commented] (MESOS-6183) mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images
[ https://issues.apache.org/jira/browse/MESOS-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15498298#comment-15498298 ] yongyu commented on MESOS-6183: --- I am launching docker. I use docker daemon with "--insecure-registry :5000" to launch docker, it is ok. But i use mesos Containerizer to lauch docker, it can not support private registry. > 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)
[jira] [Commented] (MESOS-6183) mesos's Unified Containerizer cannot set "--insecure-registry" when provisioning images
[ https://issues.apache.org/jira/browse/MESOS-6183?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15496498#comment-15496498 ] yongyu commented on MESOS-6183: --- I get the error: Subscribed with ID 'fd64c22d-cca5-4a65-b275-fef05fc63730-0920' Submitted task 'test_mesos' to agent 'fd64c22d-cca5-4a65-b275-fef05fc63730-S10' Received status update TASK_FAILED for task 'test_mesos' message: 'Failed to launch container: Failed to perform 'curl': curl: (35) SSL received a record that exceeded the maximum permissible length. ; Container destroyed while provisioning images' source: SOURCE_AGENT reason: REASON_CONTAINER_LAUNCH_FAILED > 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 > > mesos's Unified Containerizer cannot set "--insecure-registry" when > provisioning images -- This message was sent by Atlassian JIRA (v6.3.4#6332)
