Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

docker-compose instructions do not work

See original GitHub issue

Describe the bug While following the instructions for using WebAnno with docker-compose, as discussed here: https://webanno.github.io/webanno/releases/3.5.7/docs/admin-guide.html#_connecting_to_a_mysql_database, there are numerous runtime errors in the log, and trying to connect to localhost:8080 results in “no data received”.

To Reproduce Steps to reproduce the behavior:

Go to https://webanno.github.io/webanno/releases/3.5.7/docs/admin-guide.html#_connecting_to_a_mysql_database
Follow the steps starting with “We provide a docker-compose example file, which combines the two containers.”

Expected behavior Opening localhost:8080 connects to the working instance of WebAnno.

Screenshots N/A

Please complete the following information:

Today’s version of documentation
OS: macOS
Browser: chrome

Additional context It appears that docker-compose.yml is using webanno/webanno-snapshots:latest, which is 2 years old: https://github.com/webanno/webanno/blob/master/webanno-webapp/src/main/docker/docker-compose.yml#L31.

Replacing that line with webanno/webanno:3.5.6 results in everything working as expected. Can someone confirm this is the right way to fix this issue? I am a bit surprised no one ran into this, since it would seem that docker-compose is absolutely the easiest way to configure an instance.

Overall, thanks for the great documentation - I was able to get started in rather short time!

Issue Analytics

State:
Created 4 years ago
Comments:5 (3 by maintainers)

Top GitHub Comments

1reaction

reckartcommented, Jul 15, 2019

Ok, then we’d better do the thing of auto-inserting the version properly.

0reactions

fedorovcommented, Jul 15, 2019

I believe it does mean the docker will always use the latest version, but it is also more error prone, since it is impossible to control the environment - the version can effectively switch underneath. From what I know, in production setting, the use of latest is discouraged. When I experimented with it, I was also not sure if latest is the same as the version with the highest number, and was also not sure about your version numbering conventions (e.g., some projects use odd numbers to designate pre-releases), so that’s why I tried 3.5.6.

I think it is fair to change to latest, and add a note in the documentation that production deployments should use the latest numbered version instead.

But I also do not consider myself too familiar with the docker, and would happily defer to an expert on the subject matter.

Top Results From Across the Web

Try Docker Compose - Docker Documentation

Try Docker Compose. This tutorial is designed to introduce the key concepts of Docker Compose whilst building a simple Python web application.

Why is Docker installed but not Docker Compose?

Follow the instructions from the link, which involve running the curl command in your terminal to download the binaries. These step-by-step instructions are...

docker-compose up doesn't rebuild image although Dockerfile ...

If it's not in a volume, I guess it could just be that the lock was never removed. Compose will try to start...

Use Docker Compose to work with multiple containers

By default, the Docker extension does not do any volume mounting for debugging components. There's no need for it in .NET or Node.js,...

Installing Locally Using Docker Compose - Apache Superset

Install Docker on Linux by following Docker's instructions for whichever flavor of Linux suits you. Because docker-compose is not installed as part of...