starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-16 05:34:07 +03:00
Code Issues 23 Packages Projects Releases 44 Wiki Activity

Assign GPUs to containers via /dev/dri/by-path/ instead #1351

New Issue
Closed
opened 2026-02-05 00:26:33 +03:00 by OVERLORD · 12 comments
OVERLORD commented 2026-02-05 00:26:33 +03:00
Owner
Copy Link

Originally created by @danielwsky on GitHub (Jul 27, 2025).

Originally assigned to: @MickLesk on GitHub.

📌 Task summary

Refactor the way cards and renders are assigned to container (and VMs maybe) trough /dev/dri/by-path/ directory

📋 Task details

I've recently been encountering issues with container initialization due to the absence of "card0" in /dev/dri. The specific error I'm encountering is:

TASK ERROR: Device /dev/dri/card0 does not exist

The root cause of this issue seems to be Proxmox's inconsistent assignment of the GPU, alternating between card0 and card1. After some troubleshooting, I discovered that the /dev/dri/by-path/ directory, which references GPUs by their PCI address, provides a more reliable solution. By adjusting the container configuration to search for the hardware location instead of relying on the card index (card0 or card1), I managed to resolve the issue.

Image

Given this understanding, I propose that the Proxmox VM and container creation script be improved to support GPU identification by PCI address. This would enhance reliability in configuring GPU passthrough, especially in environments with multiple GPUs.

Additionally, it would be highly beneficial if the script allowed users to select which GPU they want to use during the creation of a new VM or container. This would provide extra flexibility and control, particularly on systems equipped with several graphics units.

Please consider these suggestions to enhance the robustness and functionality of the current script:

PCI Address Identification: Change the method of GPU identification to utilize the PCI address found in /dev/dri/by-path/.
User-Selectable GPU: Include an option in the script that allows users to specify which GPU should be used when creating a VM or container.

These improvements would not only resolve the current issue but also increase the flexibility and reliability of the VM and container creation process on Proxmox.

Originally created by @danielwsky on GitHub (Jul 27, 2025). Originally assigned to: @MickLesk on GitHub. ### 📌 Task summary Refactor the way cards and renders are assigned to container (and VMs maybe) trough /dev/dri/by-path/ directory ### 📋 Task details I've recently been encountering issues with container initialization due to the absence of "card0" in /dev/dri. The specific error I'm encountering is: TASK ERROR: Device /dev/dri/card0 does not exist The root cause of this issue seems to be Proxmox's inconsistent assignment of the GPU, alternating between card0 and card1. After some troubleshooting, I discovered that the /dev/dri/by-path/ directory, which references GPUs by their PCI address, provides a more reliable solution. By adjusting the container configuration to search for the hardware location instead of relying on the card index (card0 or card1), I managed to resolve the issue. <img width="432" height="40" alt="Image" src="https://github.com/user-attachments/assets/f5887d67-086b-430e-ad09-6b71b0f1bf75" /> Given this understanding, I propose that the Proxmox VM and container creation script be improved to support GPU identification by PCI address. This would enhance reliability in configuring GPU passthrough, especially in environments with multiple GPUs. Additionally, it would be highly beneficial if the script allowed users to select which GPU they want to use during the creation of a new VM or container. This would provide extra flexibility and control, particularly on systems equipped with several graphics units. Please consider these suggestions to enhance the robustness and functionality of the current script: PCI Address Identification: Change the method of GPU identification to utilize the PCI address found in /dev/dri/by-path/. User-Selectable GPU: Include an option in the script that allows users to specify which GPU should be used when creating a VM or container. These improvements would not only resolve the current issue but also increase the flexibility and reliability of the VM and container creation process on Proxmox.
OVERLORD commented 2026-02-05 00:26:40 +03:00
Author
Owner
Copy Link

@webmogul1 commented on GitHub (Aug 11, 2025):

@danielwsky Are you using plex by any chance?
I can't get it to work if I use /dev/dri/by-path.

Edit: I guess I found the problem: https://github.com/tteck/Proxmox/discussions/3235#discussioncomment-9929434

@webmogul1 commented on GitHub (Aug 11, 2025): @danielwsky Are you using plex by any chance? I can't get it to work if I use /dev/dri/by-path. Edit: I guess I found the problem: https://github.com/tteck/Proxmox/discussions/3235#discussioncomment-9929434
OVERLORD commented 2026-02-05 00:26:42 +03:00
Author
Owner
Copy Link

@danielwsky commented on GitHub (Aug 11, 2025):

@danielwsky Are you using plex by any chance? I can't get it to work if I use /dev/dri/by-path.

Edit: I guess I found the problem: tteck/Proxmox#3235 (comment)

I'm using Jellyfin and Ollama. Did you use the whole pci address? Eg /dev/dri/by-path/pci-0000:xx:00.0-card
You should be able to see your device pci address by cd /dev/dri/by-path/ then ls

If you have more than one gpu, I would suggest to check lspci | grep VGA or something like that

@danielwsky commented on GitHub (Aug 11, 2025): > [@danielwsky](https://github.com/danielwsky) Are you using plex by any chance? I can't get it to work if I use /dev/dri/by-path. > > Edit: I guess I found the problem: [tteck/Proxmox#3235 (comment)](https://github.com/tteck/Proxmox/discussions/3235#discussioncomment-9929434) I'm using Jellyfin and Ollama. Did you use the whole pci address? Eg /dev/dri/by-path/pci-0000:xx:00.0-card You should be able to see your device pci address by cd /dev/dri/by-path/ then ls If you have more than one gpu, I would suggest to check lspci | grep VGA or something like that
OVERLORD commented 2026-02-05 00:26:47 +03:00
Author
Owner
Copy Link

@webmogul1 commented on GitHub (Aug 11, 2025):

Yes, I did use the whole pci address.

This works.
Image

┌─(root@PLEX - 10.0.1.80)
└───[/dev/dri] # l
total 0
crw-rw---- 1 root video  226,   0 Aug 11 12:36 card0
crw-rw---- 1 root render 226, 128 Aug 11 12:36 renderD128

This does not work
Image

┌─(root@PLEX - 10.0.1.80)
└───[/dev/dri] # l
total 0
drwxr-xr-x 2 root root 80 Aug 11 13:31 by-path

┌─(root@PLEX - 10.0.1.80)
└───[/dev/dri/by-path] # l
total 0
crw-rw---- 1 root video  226,   0 Aug 11 13:31 pci-0000:01:00.0-card
crw-rw---- 1 root render 226, 128 Aug 11 13:31 pci-0000:01:00.0-render
@webmogul1 commented on GitHub (Aug 11, 2025): Yes, I did use the whole pci address. This works. <img width="383" height="54" alt="Image" src="https://github.com/user-attachments/assets/77792781-439c-4fbc-878c-75bd07882518" /> ``` ┌─(root@PLEX - 10.0.1.80) └───[/dev/dri] # l total 0 crw-rw---- 1 root video 226, 0 Aug 11 12:36 card0 crw-rw---- 1 root render 226, 128 Aug 11 12:36 renderD128 ``` This does not work <img width="508" height="57" alt="Image" src="https://github.com/user-attachments/assets/24d245bd-beee-4609-93c3-248dbabfc308" /> ``` ┌─(root@PLEX - 10.0.1.80) └───[/dev/dri] # l total 0 drwxr-xr-x 2 root root 80 Aug 11 13:31 by-path ┌─(root@PLEX - 10.0.1.80) └───[/dev/dri/by-path] # l total 0 crw-rw---- 1 root video 226, 0 Aug 11 13:31 pci-0000:01:00.0-card crw-rw---- 1 root render 226, 128 Aug 11 13:31 pci-0000:01:00.0-render ```
OVERLORD commented 2026-02-05 00:26:49 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 11, 2025):

Have the Same issue at some LXC from Dev Repo, thats the reason why i dont merge this Feature into live

@MickLesk commented on GitHub (Aug 11, 2025): Have the Same issue at some LXC from Dev Repo, thats the reason why i dont merge this Feature into live
OVERLORD commented 2026-02-05 00:26:53 +03:00
Author
Owner
Copy Link

@danielwsky commented on GitHub (Aug 12, 2025):

Yes, I did use the whole pci address.

This works. Image

┌─(root@PLEX - 10.0.1.80)
└───[/dev/dri] # l
total 0
crw-rw---- 1 root video  226,   0 Aug 11 12:36 card0
crw-rw---- 1 root render 226, 128 Aug 11 12:36 renderD128

This does not work Image

┌─(root@PLEX - 10.0.1.80)
└───[/dev/dri] # l
total 0
drwxr-xr-x 2 root root 80 Aug 11 13:31 by-path

┌─(root@PLEX - 10.0.1.80)
└───[/dev/dri/by-path] # l
total 0
crw-rw---- 1 root video  226,   0 Aug 11 13:31 pci-0000:01:00.0-card
crw-rw---- 1 root render 226, 128 Aug 11 13:31 pci-0000:01:00.0-render

That's weird, I don't have two gpus, but I've installed a RTX 2060 before.
Here's my setup:
Machinist X99 E5-RS9
Intel Xeon E5-2683 v4
4x16GB RAM
Intel Arc A770 16GB

Image Image

I've enabled Resizeble Bar too.
Actually, I started having the card0<>card1 flip when installing the Arc GPU and enabling ReBar. And after two weeks of troubleshooting I've found this "by-path" workaround.
I guess installing new pci devices mess with pci addressess.

Can you show your lspci | grep VGA result?
I would try to install Plex in my machine but I have no storage left.

@MickLesk , could this have something to do with grouping and access stuff? (I'm literally shooting in the dark, but linux problems are usually about access configs)

@danielwsky commented on GitHub (Aug 12, 2025): > Yes, I did use the whole pci address. > > This works. <img alt="Image" width="383" height="54" src="https://private-user-images.githubusercontent.com/5225701/476692967-77792781-439c-4fbc-878c-75bd07882518.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTQ5NTUyMzgsIm5iZiI6MTc1NDk1NDkzOCwicGF0aCI6Ii81MjI1NzAxLzQ3NjY5Mjk2Ny03Nzc5Mjc4MS00MzljLTRmYmMtODc4Yy03NWJkMDc4ODI1MTgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDgxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTA4MTFUMjMyODU4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9NGJlOWFlNDFlODY2ZDU1MWZlZmNhODdiYzA5OTdlZmJkMzcxZDJlNDJjOTcyMDFkOGJiNGJhNWU5Nzc2OGYyMyZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.vQpNgFwsLredaQPU8PCIqvt3GgDzX1d10povOlYn7m0"> > > ``` > ┌─(root@PLEX - 10.0.1.80) > └───[/dev/dri] # l > total 0 > crw-rw---- 1 root video 226, 0 Aug 11 12:36 card0 > crw-rw---- 1 root render 226, 128 Aug 11 12:36 renderD128 > ``` > > This does not work <img alt="Image" width="508" height="57" src="https://private-user-images.githubusercontent.com/5225701/476694271-24d245bd-beee-4609-93c3-248dbabfc308.png?jwt=eyJ0eXAiOiJKV1QiLCJhbGciOiJIUzI1NiJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3NTQ5NTUyMzgsIm5iZiI6MTc1NDk1NDkzOCwicGF0aCI6Ii81MjI1NzAxLzQ3NjY5NDI3MS0yNGQyNDViZC1iZWVlLTQ2MDktOTNjMy0yNDhkYmFiZmMzMDgucG5nP1gtQW16LUFsZ29yaXRobT1BV1M0LUhNQUMtU0hBMjU2JlgtQW16LUNyZWRlbnRpYWw9QUtJQVZDT0RZTFNBNTNQUUs0WkElMkYyMDI1MDgxMSUyRnVzLWVhc3QtMSUyRnMzJTJGYXdzNF9yZXF1ZXN0JlgtQW16LURhdGU9MjAyNTA4MTFUMjMyODU4WiZYLUFtei1FeHBpcmVzPTMwMCZYLUFtei1TaWduYXR1cmU9ZDlkYzNhMmJiYmZlNThmM2Q2MDQwYjBiZTc0MGY0MGE5YTYwOTk1MjhjOTNmNGZkNjZhNzU0ZDliY2FjNmQxMSZYLUFtei1TaWduZWRIZWFkZXJzPWhvc3QifQ.kBhp_FW_CZClM7yAPXt-TGtAu9xjBVpz5vFsaYwWWrA"> > > ``` > ┌─(root@PLEX - 10.0.1.80) > └───[/dev/dri] # l > total 0 > drwxr-xr-x 2 root root 80 Aug 11 13:31 by-path > > ┌─(root@PLEX - 10.0.1.80) > └───[/dev/dri/by-path] # l > total 0 > crw-rw---- 1 root video 226, 0 Aug 11 13:31 pci-0000:01:00.0-card > crw-rw---- 1 root render 226, 128 Aug 11 13:31 pci-0000:01:00.0-render > ``` That's weird, I don't have two gpus, but I've installed a RTX 2060 before. Here's my setup: Machinist X99 E5-RS9 Intel Xeon E5-2683 v4 4x16GB RAM Intel Arc A770 16GB <img width="484" height="63" alt="Image" src="https://github.com/user-attachments/assets/6c9212ec-6fe4-4b0f-8f39-bf7c81d1b877" /> <img width="1007" height="220" alt="Image" src="https://github.com/user-attachments/assets/dea50419-753b-4543-8a54-6651c98224db" /> I've enabled Resizeble Bar too. Actually, I started having the card0<>card1 flip when installing the Arc GPU and enabling ReBar. And after two weeks of troubleshooting I've found this "by-path" workaround. I guess installing new pci devices mess with pci addressess. Can you show your lspci | grep VGA result? I would try to install Plex in my machine but I have no storage left. @MickLesk , could this have something to do with grouping and access stuff? (I'm literally shooting in the dark, but linux problems are usually about access configs)
OVERLORD commented 2026-02-05 00:26:55 +03:00
Author
Owner
Copy Link

@webmogul1 commented on GitHub (Aug 12, 2025):

┌─(root@PLEX - 10.0.1.80)
└───[~] # lspci | grep VGA
01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 164e (rev d8)
@webmogul1 commented on GitHub (Aug 12, 2025): ``` ┌─(root@PLEX - 10.0.1.80) └───[~] # lspci | grep VGA 01:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Device 164e (rev d8) ```
OVERLORD commented 2026-02-05 00:26:58 +03:00
Author
Owner
Copy Link

@FibreFoX commented on GitHub (Nov 19, 2025):

@danielwsky After upgrading the hardware of my system, I stumbled upon a similar problem, but not related to the community scripts, but Promxox in general.

You wrote The root cause of this issue seems to be Proxmox's inconsistent assignment of the GPU, alternating between card0 and card1, which resembles the same behaviour as I am experiencing it.

Maybe instead of solving this via /dev/dri/by-path, you could tame the kernel a bit, which was referenced at some archlinux post or some random website my search engine came up with.

The reason of this behaviour (as far as I understood) might be a component called "simpledrm", which gets loaded by the kernel itself on boot. It is possible to disable this via kernel boot parameters like explained at https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_edit_kernel_cmdline

When using GRUB

  • edit Grub configuration on the Proxmox host: vi /etc/default/grub
  • add to the end of GRUP_CMDLINE_LINUX entry:
GRUP_CMDLINE_LINUX="(...) initcall_blacklist=simpledrm_platform_driver_init"

When using systemd-boot

  • edit Grub configuration on the Proxmox host: vi /etc/kernel/cmdline
  • add to the end of the parameters:
 initcall_blacklist=simpledrm_platform_driver_init

Then remember to generate the actual boot configuration:

proxmox-boot-tool refresh

After a restart of the system, you should be able to use /dev/dri/card0 "as normal" without it changing randomly.

But there is a downside that comes with this workaround: you will not be able anymore to see some boot text after selecting the kernel (due to the SimpleDRM driver not being loaded), but you can still see via dmesg.

I hope this helps 😺

@FibreFoX commented on GitHub (Nov 19, 2025): @danielwsky After upgrading the hardware of my system, I stumbled upon a similar problem, but not related to the community scripts, but Promxox in general. You wrote `The root cause of this issue seems to be Proxmox's inconsistent assignment of the GPU, alternating between card0 and card1`, which resembles the same behaviour as I am experiencing it. Maybe instead of solving this via `/dev/dri/by-path`, you could tame the kernel a bit, which was referenced at [some archlinux post](https://bbs.archlinux.org/viewtopic.php?id=287936) or [some random website](https://blog.lightwo.net/fix-gpu-identifier-randomly-setting-to-card0-or-card1-linux.html) my search engine came up with. The reason of this behaviour (as far as I understood) might be a component called "simpledrm", which gets loaded by the kernel itself on boot. It is possible to disable this via kernel boot parameters like explained at https://pve.proxmox.com/wiki/Host_Bootloader#sysboot_edit_kernel_cmdline **When using GRUB** * edit Grub configuration on the Proxmox host: `vi /etc/default/grub` * add to the end of GRUP_CMDLINE_LINUX entry: ``` GRUP_CMDLINE_LINUX="(...) initcall_blacklist=simpledrm_platform_driver_init" ``` **When using systemd-boot** * edit Grub configuration on the Proxmox host: `vi /etc/kernel/cmdline` * add to the end of the parameters: ``` initcall_blacklist=simpledrm_platform_driver_init ``` Then remember to generate the actual boot configuration: ``` proxmox-boot-tool refresh ``` After a restart of the system, you should be able to use `/dev/dri/card0` "as normal" without it changing randomly. But there is a downside that comes with this workaround: you will not be able anymore to see some boot text after selecting the kernel (due to the SimpleDRM driver not being loaded), but you can still see via `dmesg`. I hope this helps 😺
OVERLORD commented 2026-02-05 00:26:59 +03:00
Author
Owner
Copy Link

@FibreFoX commented on GitHub (Dec 5, 2025):

How is this completed via #9540 ? Maybe I am missing something?

As far as I can see, it still enumerated over /dev/dri, but not /dev/dri/by-path
c35102b0ba/misc/build.func (L2958)

@FibreFoX commented on GitHub (Dec 5, 2025): How is this completed via #9540 ? Maybe I am missing something? As far as I can see, it still enumerated over `/dev/dri`, but not `/dev/dri/by-path` https://github.com/community-scripts/ProxmoxVE/blob/c35102b0baa97b05b117f666d34ed922cfac8f17/misc/build.func#L2958
OVERLORD commented 2026-02-05 00:27:01 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 5, 2025):

After extensive testing across different hardware configurations, we've decided not to implement GPU assignment via /dev/dri/by-path/. Here's why:

Testing Results

GPU Type /dev/dri/by-path/ Status
Intel Arc ✅ Works OK
Intel N97 ❌ Fails Broken
AMD ❌ Fails Broken
NVIDIA ❌ Fails Broken

KNown Issues

  • Many applications (Plex, Jellyfin, etc.) explicitly look for /dev/dri/card0 or /dev/dri/renderD128 and don't resolve symlinks from by-path/
  • The by-path approach only works reliably on specific Intel Arc GPUs - it fails on AMD, NVIDIA, and even other Intel GPUs
  • The card0/card1 flip is a kernel-level issue caused by the simpledrm driver, not something we should work around in the container creation script

Recommended Solution

If you're experiencing the card0/card1 flip issue, the proper fix is to disable the simpledrm driver via kernel boot parameters:

For GRUB:

# Edit /etc/default/grub
GRUB_CMDLINE_LINUX_DEFAULT="quiet initcall_blacklist=simpledrm_platform_driver_init"
# Then run: update-grub && reboot

# For systemd boot: 
# Edit /etc/kernel/cmdline, append:
initcall_blacklist=simpledrm_platform_driver_init
# Then run: proxmox-boot-tool refresh && reboot

This ensures /dev/dri/card0 remains consistent across reboots.

@MickLesk commented on GitHub (Dec 5, 2025): After extensive testing across different hardware configurations, we've decided **not to implement** GPU assignment via `/dev/dri/by-path/`. Here's why: ### Testing Results | GPU Type | `/dev/dri/by-path/` | Status | |----------|---------------------|--------| | Intel Arc | ✅ Works | OK | | Intel N97 | ❌ Fails | Broken | | AMD | ❌ Fails | Broken | | NVIDIA | ❌ Fails | Broken | KNown Issues - Many applications (Plex, Jellyfin, etc.) explicitly look for `/dev/dri/card0` or `/dev/dri/renderD128` and don't resolve symlinks from `by-path/` - The `by-path` approach only works reliably on specific Intel Arc GPUs - it fails on AMD, NVIDIA, and even other Intel GPUs - The `card0`/`card1` flip is a **kernel-level issue** caused by the `simpledrm` driver, not something we should work around in the container creation script ### Recommended Solution If you're experiencing the `card0`/`card1` flip issue, the proper fix is to disable the `simpledrm` driver via kernel boot parameters: **For GRUB:** ```bash # Edit /etc/default/grub GRUB_CMDLINE_LINUX_DEFAULT="quiet initcall_blacklist=simpledrm_platform_driver_init" # Then run: update-grub && reboot # For systemd boot: # Edit /etc/kernel/cmdline, append: initcall_blacklist=simpledrm_platform_driver_init # Then run: proxmox-boot-tool refresh && reboot ``` This ensures /dev/dri/card0 remains consistent across reboots.
OVERLORD commented 2026-02-05 00:27:04 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 5, 2025):

Oh, and to clarify: we NEVER change anything in the kernel options in Proxmox. So that's out of the question for us. If a user needs it, fine. We have 2 million installations this year, and the use case is too rare for us to do anything like that.

@MickLesk commented on GitHub (Dec 5, 2025): Oh, and to clarify: we NEVER change anything in the kernel options in Proxmox. So that's out of the question for us. If a user needs it, fine. We have 2 million installations this year, and the use case is too rare for us to do anything like that.
OVERLORD commented 2026-02-05 00:27:07 +03:00
Author
Owner
Copy Link

@FibreFoX commented on GitHub (Dec 5, 2025):

Ah okay :) thanks for clarifying ... was just confused because it was labeled as "completed" by GitHub, and even was meantioned in the linked MR #9540 as "Related"

@FibreFoX commented on GitHub (Dec 5, 2025): Ah okay :) thanks for clarifying ... was just confused because it was labeled as "completed" by GitHub, and even was meantioned in the linked MR #9540 as "Related"
OVERLORD commented 2026-02-05 00:27:12 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 5, 2025):

yeah because ive refactored the whole gpu / device bypass in the new core :-)

@MickLesk commented on GitHub (Dec 5, 2025): yeah because ive refactored the whole gpu / device bypass in the new core :-)
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label Implemented in VED waiting push to Main enhancement feature investigation
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1351
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?