[Doc][Module Name] Install via Docker Compose

[155martinmoreno]

Documentation Scope

Install via Docker Compose

Describe the Change

You should add the location of the dockerfile and env files mentioned in the doc
(In this case devops/releases/lake-v0.21.0/)

Additional context

It isn't easy to find otherwise

[klesh]

Can you elaborate? Which document and section are you referring to?

[155martinmoreno]

Sorry, I meant the docs found here

[klesh]

I see.
The doc you were referring to has a link to the releases page which provides files mentioned :

[155martinmoreno]

Well, I've followed the Getting Started process again to double-check.

The Docker compose on the Release is different from the one in the devops/releases/lake-v0.21.0/ folder (seems to be the latest, but I'm probably wrong)

• docker-compose.yml (release) points to Grafana devlake.docker.scarf.sh/apache/devlake-dashboard:1.0.1 and yelds manifest unknown error.
• docker-compose.yml (in folder) points to Grafana devlake.docker.scarf.sh/apache/devlake-dashboard:v0.21.0 and works

Either the docker-compose is wrong or the doc is missing some step about signing in to a registry.

A related issue points to using latest for all images on the docker-compose, and although it works, I'm not sure it's the right call in this context

[klesh]

@155martinmoreno I see. Please use the one from the release page as shown in the screenshot I posted.
The latest release should be v1.0.2-beta5

[155martinmoreno]

Thanks for the answer, but I think I'm not being clear.

If I use the one pointed out in the screenshot, it fails with a manifest unknown error (see my previous answer).

I can fix it by changing it to latest, but you should mention this in the docs for other newcomers.

[klesh]

@155martinmoreno I just double checked the one from my screenshot, it is pointing to v1.0.2-beta5.

So, I don't understand why you were seeing 1.0.1

[155martinmoreno]

Ah, I see now.

The reason is that I'm pulling the Latest release, instead of Beta5

Do you think it's ok for Latest (1.0.1) to give manifest error? should we always point to the latest beta? does this deserve a comment in the Getting Started doc?

If not, I'll go ahead and close this thread.

Thanks for the follow-up!

[klesh]

I see... Thanks for the explanation.
I just updated the docker-compose.yml for the release 1.0.1, it should be working now.