[Request]: Provide better instructions for Docker setup and update Docker image

[rowild]

Summary

When working through this docu:
https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/docker.html#creating-a-strapi-project
the final result does

• not work
• use strapi 3.8.6

Why is it needed?

Using a v3 strapi in a v4 docu is misleading. This should be mentioned in any way so the user knows what (s)he is up to.

Also, the provided docker-compose-yml code is formatted wrongly, which leads - given the example is copy-&-pasted - to errors, when running docker-compose up.

And even after fixing that, this setup does not generate a valid URL - meaning: it is not working.

Given, that in many places the docu is very detailed and sometimes even covering very basic stuff (stuff where I would think this must be a pre-requisite or given knowledge before even starting with strapi), this particular docu could need more indications on how to get this setup running. E.g. examples how to communicate with strapi via terminal, how to deploy a docker instance to e.g. heroku, etc.

If strapi's docker image will not be updated to v4, then a guideline on how to update to v4 should be given or at least pointed to.

Suggested solution(s)

UPDATE: As I just found out, I am not the only one, who complains. So why not provide links in the documentation that are mentioned here:
strapi/strapi-docker#321
Perferably at the very top, at least for the time being.

Related issue(s)/PR(s)

No response

[stb13579]

Hi @rowild, Thanks for opening this issue and being an active contributor to the Strapi community. I plan to address this issue in the documentation during the next week.

[stb13579]

Hello @rowild, with feedback from our team, I have updated the developer docs. Please see PR #828 and/or the readme file in the Docker repository for our current recommendations regarding Docker and v4. Thanks again for your contributions to improving the Strapi Documentation.

[rowild]

@StrapiShaun Thanks for the feedback!

However, this page:
https://documentation-git-dev-docker-update-strapijs.vercel.app/developer-docs/latest/setup-deployment-guides/installation/docker.html#creating-a-strapi-project

only received a new warning at the top, but nothing else, that points to a successful way on how to get strapi docker running. The relevant information is here:
https://github.com/strapi/strapi-docker

and the first page should AT LEAST provide link with a little bit of more description to it. Something like:
"Please refer to our detailed readme at [url] for further installation steps."

Or, even better, actually DO provide ALL the installation steps required to get strapi docker running in the documentation itself. That's what IMO a documentation is for, after all.

The status quo is IMO not enough and I would vote for re-opening this issue.
Thank you!

[rowild]

Thank you, @StrapiShaun !

The main thing that is missing (or at least was missing for me) is that it is required to run

docker run -it -p 1337:1337 -v `pwd`:/srv/app strapi/strapi

which seems to install the strapi dependencies (so far only DB dependencies are installed).

(If that is wrong on my part (due to me being to impatient, because nothing happens on the CLI), than I would suggest to mention that a considerable waiting time is to be expected until all dependencies are installed.)

[stb13579]

Hi @rowild, I will check to see what we can update in the short term. Any updates that are relevant to v3 will be in the v3 documentation, not in the v4 for documentation. I will leave this issue open until I can share more information. Thanks again for your continued contributions and feedback.

[rowild]

@StrapiShaun The Docker instructions are also available in the v4 documentation:

https://docs.strapi.io/developer-docs/latest/setup-deployment-guides/installation/docker.html

An idea: Instead of providing an old, incomplete instruction, that does not fit your internal guidelines and as long as there is no v4 for docker, why not just put a link there to the v3 documentation mentioning that there is currently no v4 available? Wouldn't that solve inconsistencies with your guideline as well as reduce update work?

No sure if it woudn't be better to continue this discussion in only one place, preferably the PR #828? I leave it up to you, but if so, I can provide this idea "over there", too.

Thank you!

[pwizla]

Closing as it was handled in #828