[
https://issues.apache.org/jira/browse/HDDS-3497?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Siyao Meng resolved HDDS-3497.
------------------------------
Resolution: Not A Problem
Closing as Not A Problem. This is expected docker networking behavior rather
than an Ozone bug. A client on the host is handed datanode addresses on the
internal compose network. Either publish the datanode ports explicitly, or run
{{ozone sh}} inside a container via {{docker compose exec}} as {{run.sh}} and
the acceptance tests do.
> Host cannot access DN in the docker container when using docker-compose
> -----------------------------------------------------------------------
>
> Key: HDDS-3497
> URL: https://issues.apache.org/jira/browse/HDDS-3497
> Project: Apache Ozone
> Issue Type: Bug
> Components: docker
> Affects Versions: 1.0.0
> Reporter: Baolong Mao
> Priority: Major
> Attachments: screenshot-1.png
>
>
> Now i using docker-compose to start a ozone cluster, and i create volume and
> bucket, but i cannot put some file into this ozone cluster in my host node.
> Following is the step to reproduce.
> ozone-0.6.0-SNAPSHOT/compose/ozone/run.sh
> pwd=ozone-0.6.0-SNAPSHOT
> bin/ozone sh vol create myvol
> bin/ozone sh bucket create myvol/mybucket
> bin/ozone sh key put /myvol/mybucket/README.md README.md
> The last command stuck.
> And i do some debug work. I see the ratis pipeline here with nodes using
> ip:port, in the host node, i cannot access these ip in another network
> !screenshot-1.png!
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
