--- description: Smoketest page title: Testing page sitemap: false toc_min: 1 --- Welcome to the Docker documentation test page! This is a demo of components, tags, styles, tools, and strategies we use for the docs. We explain the code behind the published page and demo the effects. So, if you want to see, for example, how admonitions and notes are coded in markdown, read the section on [Admonitions (notes)](test.md#admonitions-notes) on the web published page and study the pre-processed `test.md` to see how they are implemented. The Docker documentation team uses this page as "note to self" reminders. Since we invite docs suggestions and contributions from the community, we've always made the test page generally available. If you want to understand how something in the docs is coded, use this page is as a resource. If, in the course of making docs updates and suggestions, you develop a new strategy or component for the docs, feel free to add a demo and explanation to this test page and submit a PR for it so we can review and discuss it. Cool? Let's dive in! # Heading 1 Most pages don't actually have a H1 heading. The page title from the metadata is automatically inserted. We have included it here to show all heading levels, and set front matter as `toc_min: 1` so that it shows in the navigation bar (on-page topics). ## Heading 2 By default, this is the highest heading included in the right navigation bar. To include more heading levels, set `toc_min: 1` in the page's front-matter (as is done on this `test.md` page). You can go all the way to 6, but if `toc_min` is geater than `toc_max` then no headings are shown. ### Heading 3 This is the lowest heading included in the right-nav, by default. To include more heading levels, set `toc_max: 4` in the page's front-matter. You can go all the way to 6. #### Heading 4 This heading is not included in the right-nav. To include it set `toc_max: 4` in the page's front-matter. ##### Heading 5 This heading is not included in the right-nav. To include it set `toc_max: 5` in the page's front-matter. ###### Heading 6 This is probably too many headings. Try to avoid it. This heading is not included in the right-nav. To include it set `toc_max: 6` in the page's front-matter. ## Typography Plain block of text. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum. **Inline text styles**: - **bold** - _italic_ - ***bold italic*** - ~~strikethrough~~ - underline - _underline italic_ - **underline bold** - ***underline bold italic*** - `monospace text` - **`monospace bold`** ## Links and images ### Links - [a markdown link](https://docker.com/) https://github.com/docker/docker.github.io/tree/master/docker-cloud/images - [a markdown link that opens in a new window](https://docker.com/){: target="_blank" rel="noopener" class="_" } (the `class="_"` trick prevents Atom from italicizing the whole rest of the file until it encounters another underscore.) - [a markdown link to a custom target ID](#custom-target-id) - an HTML link - an HTML link that opens in a new window - A link to a Github PR in `docker/docker`: {% include github-pr.md pr=28199 %} - A link to a Github PR in `docker/docker.github.io`: {% include github-pr.md repo=docker.github.io pr=9999 %} - You can specify `org=foo` to use a Github organization other than Docker - A link to an auto-generated reference page that we pull in during docs builds: [/engine/reference/builder/#env](/engine/reference/builder/#env). - If you can't find a reference page in the `docker.github.io` GitHub repository, but see it out on `docs.docker.com`, you can surmise that it's probably auto-generated from the codebase. (FYI, to view the markdown source for the file, just click **Edit this page** on `docs.docker.com`. But don't use that URL in your docs.) - Go to the file in a web browser, grab everything after the domain name from the URL, and use that as the link in your docs file. - Keep in mind that this link doesn't resolve until you merge the PR and your docs are published on [docs.docker.com](/). {: id="custom-target-id"} #### Using a custom target ID This topic has a custom target ID above its heading that can be used to link to it, in addition to, or instead of, the default concatenated heading style. The format of this ID is `{: id="custom-target-id"}`. You can use custom targets to link to headings or even paragraphs. You link to it as you would any other link, using `#custom-target-id` as the ultimate target. An example of a custom target ID in the documentation is the topic on [Compose file version 2 topic on CPU and other resources](compose/compose-file/compose-file-v2.md#cpu-and-other-resources). It has a long heading that breaks the normal markdown linking mechanism, so we added a custom ID above the target heading. ### Images - A small cute image: ![a small cute image](/images/footer_moby_icon.png) - A small cute image that is a link. The extra newline here makes it not show inline: [![a small cute image](/images/footer_moby_icon.png)](https://www.docker.com/) - A big wide image: ![a pretty wide image](/images/banner_image_24512.png) - The same as above but using HTML: [Some Bootstrap image classes](https://v4-alpha.getbootstrap.com/content/images/) might be interesting. You can use them with Markdown or HTML images. - An image using the Bootstrap "thumbnail" class: ![an image as a thumbnail](/images/footer_moby_icon.png){: class="img-thumbnail" } - The same one, but using HTML: ## Videos You can add a link to a YouTube video like this: [Docker 101: Introduction to Docker](https://www.youtube.com/watch?v=V9IJj4MzZBc "Docker 101: Introduction to Docker"){:target="_blank" rel="noopener" class="_"} To make the `.png` shown above, first take a screen snap of the YouTube video you want to use, then use a graphics app to overlay a play button onto the image. For the overlay, you can use the play button at [/docker-cloud/images/](https://github.com/docker/docker.github.io/tree/master/docker-cloud/images). ## Lists - Bullet list item 1 - Bullet list item 2 * Bullet list item 3 1. Numbered list item 1. Two spaces between the period and the first letter helps with alignment. 2. Numbered list item 2. Let's put a note in it. >**Note**: We did it! 3. Numbered list item 3 with a code block in it. You need the blank line before the code block happens. ```bash $ docker run hello-world ``` 4. Numbered list item 4 with a bullet list inside it and a numbered list inside that. - Sub-item 1 - Sub-item 2 1. Sub-sub-item 1 2. Sub-sub-item-2 with a table inside it because we like to party! Indentation is super important. |Header 1 | Header 2 | |---------|----------| | Thing 1 | Thing 2 | | Thing 3 | Thing 4 | ## Tables Some tables in markdown and html. | Permission level | Access | |:-------------------------------------------------------------------------|:-------------------------------------------------------------| | **Bold** or _italic_ within a table cell. Next cell is empty on purpose. | | | | Previous cell is empty. A `--flag` in mono text. | | Read | Pull | | Read/Write | Pull, push | | Admin | All of the above, plus update description, create and delete | The alignment of the cells in the source doesn't really matter. The ending pipe character is optional (unless the last cell is supposed to be empty). The header row and separator row are optional. If you need block-level HTML within your table cells, such as multiple paragraphs, lists, sub-tables, etc, then you need to make a HTML table. This is also the case if you need to use rowspans or colspans. Try to avoid setting styles directly on your tables! If you set the width on a `
Left channel | Right channel |
---|---|
This is some test text. This is more text on a new line. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. |
This is some more text about the right hand side. There is a link here to the Docker Experimental Features README on GitHub. In tables, links need to be ``. Lorem ipsum dolor sit amet, consectetur adipisicing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. |
$ docker run hello-world
Unable to find image 'hello-world:latest' locally
latest: Pulling from library/hello-world
b04784fba78d: Pull complete
Digest: sha256:f3b3b28a45160805bb16542c9531888519430e9e6d6ffc09d72261b0d26ff74f
Status: Downloaded newer image for hello-world:latest
Hello from Docker!
This message shows that your installation appears to be working correctly.
To generate this message, Docker took the following steps:
1. The Docker client contacted the Docker daemon.
2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
3. The Docker daemon created a new container from that image which runs the
executable that produces the output you are currently reading.
4. The Docker daemon streamed that output to the Docker client, which sent it
to your terminal.
To try something more ambitious, you can run an Ubuntu container with:
$ docker run -it ubuntu bash
Share images, automate workflows, and more with a free Docker ID:
https://hub.docker.com/
For more examples and ideas, visit:
https://docs.docker.com/engine/userguide/
Lorem ipsum dolor sit amet, consectetur adipiscing elit, sed do eiusmod tempor incididunt ut labore et dolore magna aliqua. Ut enim ad minim veniam, quis nostrud exercitation ullamco laboris nisi ut aliquip ex ea commodo consequat. Duis aute irure dolor in reprehenderit in voluptate velit esse cillum dolore eu fugiat nulla pariatur. Excepteur sint occaecat cupidatat non proident, sunt in culpa qui officia deserunt mollit anim id est laborum.