Elgato_dark/podman-desktop
1
0
Fork 0
mirror of https://github.com/podman-desktop/podman-desktop synced 2026-04-21 17:47:22 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 10

docs: use unambiguous name for Apple silicon in GPU docs (#14027)

Browse source 
* docs: Use unambiguous name for Apple silicon in GPU docs

Use the term from Apple's style guide to refer to Apple silicon
since "Silicon" by itself is ambiguous and confusing.

https://help.apple.com/pdf/applestyleguide/en_US/apple-style-guide.pdf

Remove the plural abbreviation for "OS" since it was written two different
ways close together and it's less confusing to use the words rather than
the abbreviation.

Signed-off-by: Sam Doran <sdoran@redhat.com>
This commit is contained in:
Sam Doran 2025-09-24 13:25:18 -04:00 committed by GitHub
parent 5c18020c20
commit 39ab0f14f9
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
2 changed files with 8 additions and 8 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

6
website/docs/podman/gpu.md
View file

@ -121,11 +121,11 @@ You might need to restart your Podman machine.
- [NVIDIA Container Toolkit Installation](https://docs.nvidia.com/datacenter/cloud-native/container-toolkit/latest/install-guide.html#installing-with-yum-or-dnf)
</TabItem>
<TabItem value="macOS" label="macOS (Silicon)" className="markdown">
<TabItem value="macOS" label="macOS (Apple silicon)" className="markdown">
#### Prerequisites
- macOS Silicon (M1 or later)
- Mac with Apple silicon (M1 or later)
#### Procedure
@ -216,7 +216,7 @@ Important note that the virtualized GPU (Virtio-GPU Venus (Apple M1 Pro)) only s
4. Configure SELinux (if applicable)
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.
On SELinux-enabled operating systems, such as the Fedora family, the default policy usually disallows containers to have direct access to devices. We make sure it's allowed.
Check whether SELinux is installed and enabled:

10
website/docs/troubleshooting/troubleshooting-podman-on-macos.md
View file

@ -40,7 +40,7 @@ or any similar error denoting that Podman Engine does not exist.
#### Explanation
The Podman Installer and Homebrew use different locations to store the Podman Engine files in the file system. For example, Podman Installer installs Podman Engine in the path `/opt/podman` whereas Homebrew uses the path `/usr/local` for macOS Intel, `/opt/homebrew` for Apple Silicon and `/home/linuxbrew/.linuxbrew` for Linux.
The Podman Installer and Homebrew use different locations to store the Podman Engine files in the file system. For example, Podman Installer installs Podman Engine in the path `/opt/podman` whereas Homebrew uses the path `/usr/local` for macOS Intel, `/opt/homebrew` for Apple silicon and `/home/linuxbrew/.linuxbrew` for Linux.
#### Solution
@ -68,11 +68,11 @@ Here, you would replace `path-where-podman-exists` with the output of `which pod
You can now proceed for a fresh installation of Podman Desktop
## Podman machine on Apple Silicon
## Podman machine on Apple silicon
#### Issue
If you are using an Apple Silicon and brew, you might encounter the following error when starting Podman from Podman Desktop
If you are using an Apple silicon and brew, you might encounter the following error when starting Podman from Podman Desktop
```shell-session
Error: qemu exited unexpectedly with exit code 1, stderr: qemu-system-x86_64: invalid accelerator hvf
@ -163,9 +163,9 @@ Keep your brew-based installation and apply one of these workarounds:
- [Homebrew issue #140244](https://github.com/Homebrew/homebrew-core/issues/140244).
- [Podman issue #19708](https://github.com/containers/podman/issues/19708).
## On Apple Silicon, the Podman Machine does not start
## On Apple silicon, the Podman Machine does not start
On Apple Silicon, when Podman Machine starts, it stays indefinitely blocked with a _Waiting for VM_ message.
On Apple silicon, when Podman Machine starts, it stays indefinitely blocked with a _Waiting for VM_ message.
#### Solution