| Both sides previous revision Previous revision | |
| articles:proxmoxaudio [2026/02/28 21:05] – [Proxmox LXC Containers with Audio] hjr | articles:proxmoxaudio [2026/02/28 21:12] (current) – hjr |
|---|
| However: the "shenanigans" involved are really quite //elaborate// and complex shenanigans and this is definitely not for the faint-hearted! Each distro has its own quirks and peculiarities. I'll document those for Arch, Fedora, Ubuntu and Linux Mint: the same //principles// then apply to any other distro, but the specifics will need to be worked out by yourself according to what otherwise breaks or works! | However: the "shenanigans" involved are really quite //elaborate// and complex shenanigans and this is definitely not for the faint-hearted! Each distro has its own quirks and peculiarities. I'll document those for Arch, Fedora, Ubuntu and Linux Mint: the same //principles// then apply to any other distro, but the specifics will need to be worked out by yourself according to what otherwise breaks or works! |
| |
| | I'll begin by discussing two ways of adding shared, on-the-network storage to your Proxmox environment: managed storage and un-managed storage. This is something you'll do once-only to your Proxmox host and all your containers will benefit from it thereafter, so it's as well to get this out of the way up-front before tackling distro-specific container issues. |
| |
| | ===== 2.0 Adding Managed NFS Storage to the Proxmox Host ===== |
| | NFS storage is added to a Proxmox environment in two distinct ways, depending on whether you want Proxmox to manage them or whether you just want Proxmox to //access// them (perhaps even in read-only mode). |
| |
| ===== 2.0 Adding NFS Storage to the Proxmox Host ===== | Managed network storage is created via the Proxmox web interface; unmanaged storage has to be created using the command line. Managed storage is what you want when you need to back up your containers and virtual machines: it's storage that Proxmox will create a number of folders in and keep an eye on automatically once it's been created. This is //not//, therefore, how you get NFS storage visible to containers and virtual machines: it's only network storage that the Proxmox host itself will be able to see and use. |
| We start with this situation: | |
| | So, with all that out of the way, we start with this situation: |
| |
| {{ :articles:screenshot_2026-02-28_at_17.09.22.png?direct&600 |}} | {{ :articles:screenshot_2026-02-28_at_17.09.22.png?direct&600 |}} |
| {{ :articles:screenshot_2026-02-28_at_17.26.03.png?direct&600 |}} | {{ :articles:screenshot_2026-02-28_at_17.26.03.png?direct&600 |}} |
| |
| My 'Copland' host is allowed to see the NAS for backups and restores -and that's it. It cannot see the NAS's music collection for use by containers. That's a separate sort of setup that, oddly, cannot be done using the web GUI interface, but requires a trip to the command line. | My 'Copland' host is allowed to see the NAS for backups and restores -and that's it. |
| |
| ===== 3.0 Mounting a non-managed NAS Share ===== | ===== 3.0 Adding an unmanaged NAS Share to the Proxmox Host ===== |
| So, now click on the Proxmox host item in the Web Gui (i.e., the one directly under 'datacenter': in my case, that's "Copland"): | So, now click on the Proxmox host item in the Web Gui (i.e., the one directly under 'datacenter': in my case, that's "Copland"): |
| |