Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Inconsistencies between the docker hub documentation and its related image #24

Open
swiss-knight opened this issue Jan 29, 2020 · 0 comments

Comments

@swiss-knight
Copy link

Hi,

I have run into some (incomprehensible) troubles while trying to follow the docker hub documentation (at https://hub.docker.com/r/geodata/cesium-terrain-server/ ) to execute the code from the docker image I pulled from there.

For example, if I map the port :80 nothing happens. Not even an error, just like if no communication occurs between the container and my localhost. I figured out that I have to map the port :8000 of the container to my host machine, which is not described in the documentation.

Another thing is that I was not able to found anything related to Apache within the logs (e.g. in /var/log) on the container itself, yet the doc says:

Within the container an instance of the Apache web server serves up the relevant server side assets provided by Cesium.js.

Or:

All requests to the apache server are logged to /var/log/apache2/other_vhosts_access.log.

So I guess there is some inconsistencies between the docker image and its documentation.
Maybe it should be rewritten to fit the real behavior of the container (which actually seems to work really fine)?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant