Consideration for using "docker init" command in Docker documentation

[D7x7z49]

Is this a docs issue?

• [X] My issue is about the documentation content or website

Type of issue

I can't find what I'm looking for

Description

I would like to suggest an improvement to the Docker documentation, specifically in the section regarding the usage of the "docker init" command. Currently, the documentation assumes that users have Docker Desktop installed, which may not always be the case. Users without Docker Desktop installed may not be able to execute "docker init" and may miss out on essential information regarding file creation.

This is a tutorial-type document, and it should provide options for learners to follow along even if they are not using "docker init." One simple solution would be to include code snippets of the file content, allowing users to create the files manually. Additionally, this approach ensures that readers can verify if the file contents match, which can be crucial for different versions and iterations.

I believe this adjustment would greatly enhance the accessibility and usability of the Docker documentation, catering to a wider range of users and scenarios.

One additional point to emphasize is that the issue exists in every subsection of https://docs.docker.com/language/. The mention of "docker init" may cause a lack of symmetry in information for readers across each subsection. This inconsistency can lead to confusion and hinder the learning experience. Therefore, it's essential to address this issue across all subsections to ensure uniformity and clarity in the documentation.

Location

https://docs.docker.com/language/

Suggestion

To address this issue, I propose adding code snippets of the file content for users who may not have Docker Desktop installed. This will allow them to manually create the required files, ensuring they can follow along with the tutorial without relying solely on "docker init."