You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: website/docs/discover-podman-desktop.md
+5-1
Original file line number
Diff line number
Diff line change
@@ -86,7 +86,11 @@ For more details, refer to [From containers to Kubernetes](/docs/kubernetes).
86
86
87
87
### Manage Docker compatibility
88
88
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.
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).
216
216
217
217
4. Configure SELinux (if applicable)
218
218
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.
220
220
221
-
Check whether SELinux is installed and enabled:
221
+
Check whether SELinux is installed and enabled:
222
222
223
-
```sh
224
-
$ getenforce
225
-
```
223
+
```sh
224
+
$ getenforce
225
+
```
226
226
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:
0 commit comments