Skip to content

Commit dfd5c21

Browse files
authored
docs(website): fixed formatting issues (podman-desktop#11638)
* docs(website): fixed formatting issues Signed-off-by: Shipra Singh <[email protected]> * docs(website): updated a screenshot Signed-off-by: Shipra Singh <[email protected]> * docs(website): formatted text Signed-off-by: Shipra Singh <[email protected]> --------- Signed-off-by: Shipra Singh <[email protected]>
1 parent 6e9895a commit dfd5c21

File tree

4 files changed

+26
-21
lines changed

4 files changed

+26
-21
lines changed
Loading

website/docs/discover-podman-desktop.md

+5-1
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,11 @@ For more details, refer to [From containers to Kubernetes](/docs/kubernetes).
8686

8787
### Manage Docker compatibility
8888

89-
Docker compatibility is a way to configure an environment in which you can run your Docker applications, commands, and tools on a Podman engine without reconfiguration. It encompasses two stages. You first [import your saved containers](/docs/migrating-from-docker/importing-saved-containers) into Podman Desktop using CLI and then access the [Docker Compatibility settings](/docs/migrating-from-docker/managing-docker-compatibility) to configure a Docker-compatible environment based on your needs.
89+
Docker compatibility is a way to configure an environment in which you can run your Docker applications, commands, and tools on a Podman engine without reconfiguration. It encompasses the following stages:
90+
91+
1. [Import your saved containers](/docs/migrating-from-docker/importing-saved-containers) into Podman Desktop using the CLI.
92+
1. Enable the [Docker compatibility](/docs/migrating-from-docker/customizing-docker-compatibility#enable-docker-compatibility) feature.
93+
1. Access the [Docker Compatibility settings](/docs/migrating-from-docker/managing-docker-compatibility) to configure a Docker-compatible environment.
9094

9195
### Integrate your tools using extensions
9296

website/docs/podman/gpu.md

+20-20
Original file line numberDiff line numberDiff line change
@@ -198,38 +198,38 @@ Important note that the virtualized GPU (Virtio-GPU Venus (Apple M1 Pro)) only s
198198

199199
3. Generate the CDI Specification file for Podman:
200200

201-
This file is saved either to /etc/cdi or /var/run/cdi on your Linux distribution and is used for Podman to detect your GPU(s).
201+
This file is saved either to /etc/cdi or /var/run/cdi on your Linux distribution and is used for Podman to detect your GPU(s).
202202

203-
Generate the CDI file:
203+
Generate the CDI file:
204204

205-
```sh
206-
$ nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml
207-
```
205+
```sh
206+
$ nvidia-ctk cdi generate --output=/etc/cdi/nvidia.yaml
207+
```
208208

209-
Check the list of generated devices:
209+
Check the list of generated devices:
210210

211-
```sh
212-
$ nvidia-ctk cdi list
213-
```
211+
```sh
212+
$ nvidia-ctk cdi list
213+
```
214214

215-
More information as well as troubleshooting tips can be found [on the official NVIDIA CDI guide](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/cdi-support.html).
215+
More information as well as troubleshooting tips can be found [on the official NVIDIA CDI guide](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/cdi-support.html).
216216

217217
4. Configure SELinux (if applicable)
218218

219-
On SELinux-enabled OSes, such as OSs from the Fedora family, the default policy usually disallows containers to have direct access to devices. We make sure it's allowed.
219+
On SELinux-enabled OSes, such as OSs from the Fedora family, the default policy usually disallows containers to have direct access to devices. We make sure it's allowed.
220220

221-
Check whether SELinux is installed and enabled:
221+
Check whether SELinux is installed and enabled:
222222

223-
```sh
224-
$ getenforce
225-
```
223+
```sh
224+
$ getenforce
225+
```
226226

227-
- If `getenforce` is not found or its output is `Permissive` or `Disabled`, no action is needed.
228-
- If the output is `Enforcing`, configure SELinux to enable device access for containers:
227+
- If `getenforce` is not found or its output is `Permissive` or `Disabled`, no action is needed.
228+
- If the output is `Enforcing`, configure SELinux to enable device access for containers:
229229

230-
```sh
231-
$ sudo setsebool -P container_use_devices true
232-
```
230+
```sh
231+
$ sudo setsebool -P container_use_devices true
232+
```
233233

234234
#### Verification
235235

website/tutorial/index.md

+1
Original file line numberDiff line numberDiff line change
@@ -48,4 +48,5 @@ Before going through each tutorial, familiarize yourself with the key UI compone
4848
- [Interacting with a database server](/tutorial/interacting-with-a-database-server)
4949
- [Managing your application resources](/tutorial/managing-your-application-resources)
5050
- [Running an AI application](/tutorial/running-an-ai-application)
51+
- [Creating an extension](/tutorial/creating-an-extension)
5152
- [Testcontainers with Podman](/tutorial/testcontainers-with-podman)

0 commit comments

Comments
 (0)