You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@ozone.apache.org by "runzhiwang (Jira)" <ji...@apache.org> on 2019/12/27 05:27:00 UTC
[jira] [Updated] (HDDS-2814) Fail to connect s3g in docker
container with network proxy
[ https://issues.apache.org/jira/browse/HDDS-2814?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
runzhiwang updated HDDS-2814:
-----------------------------
Summary: Fail to connect s3g in docker container with network proxy (was: Can not connect to s3g in docker container with network proxy)
> Fail to connect s3g in docker container with network proxy
> -----------------------------------------------------------
>
> Key: HDDS-2814
> URL: https://issues.apache.org/jira/browse/HDDS-2814
> Project: Hadoop Distributed Data Store
> Issue Type: Bug
> Components: test
> Reporter: runzhiwang
> Priority: Major
> Attachments: image-2019-12-27-11-45-39-015.png
>
>
> When run compose/ozones3-haproxy/test.sh in my machine which connect network by proxy, it fails to curl [http://scm:9876|http://scm:9876/static/bootstrap-3.4.1/js/bootstrap.min.js] as the image show. Because curl try to resolve [http://scm:9876|http://scm:9876/static/bootstrap-3.4.1/js/bootstrap.min.js] by the network proxy, which caused fail. Actually, [http://scm:9876|http://scm:9876/] is the local realm name used by the docker container which should not resolved by proxy.
> !image-2019-12-27-11-45-39-015.png! .
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
---------------------------------------------------------------------
To unsubscribe, e-mail: ozone-issues-unsubscribe@hadoop.apache.org
For additional commands, e-mail: ozone-issues-help@hadoop.apache.org