[
https://issues.apache.org/jira/browse/TINKERPOP-2086?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16673047#comment-16673047
]
Florian Hockmann commented on TINKERPOP-2086:
---------------------------------------------
Hmm, then it's probably simply a Docker for Windows issue. I just tried it with
a nginx container and had the same behaviour. Networking with Docker and
especially in combination with Windows really isn't nice :-/
So I'm closing this as it doesn't make much sense to publish the port only for
Windows devs, especially since {{TINKERPOP_DOCKER_OPTS}} already provides a
good solution that I wasn't aware of when I created the ticket. Thanks Stephen
and Robert for confirming that it's working as expected (on Linux).
> Publish docs port for docker/build.sh -d
> ----------------------------------------
>
> Key: TINKERPOP-2086
> URL: https://issues.apache.org/jira/browse/TINKERPOP-2086
> Project: TinkerPop
> Issue Type: Improvement
> Components: build-release
> Affects Versions: 3.2.10
> Reporter: Florian Hockmann
> Priority: Minor
>
> The easiest way to generate our docs is by using Docker via
> {{./docker/build.sh -d}} which generates the docs. However, to actually
> verify that changes to the docs look as expected, one has to manually inspect
> the generated docs.
> We could simply publish port 80 (maybe to another port like 8080) to make the
> docs accessible on the host for manual inspection.
> A workaround is currently to start another container that exposes the port
> and relays to the TinkerPop container with socat:
> {code}
> docker run -p 8080:80 --link [tinkerpop_container]:target alpine/socat
> tcp-listen:80,fork,reuseaddr tcp-connect:target:80{code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
