SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-07-01 19:52:11 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

OpenMediaVault container usability #22

New Issue
Closed
opened 2025-11-20 04:42:39 -05:00 by saavagebueno · 1 comment
saavagebueno commented 2025-11-20 04:42:39 -05:00
Owner
Copy Link

Originally created by @sartoricz on GitHub (Nov 8, 2024).

Please verify that you have read and understood the guidelines.

yes

A clear and concise description of the issue.

I deployed LXC container of OpenMediaVault and tried to add external disk. After searching some discussions I go to this:
https://forum.openmediavault.org/index.php?thread/51217-trying-to-access-additional-drives-via-proxmox-with-lxc/

It seems that deploying OMV into LXC is not the preferred way and this script should be removed/replaced with VM deployment.

What settings are you currently utilizing?

Default Settings

Which Linux distribution are you employing?

Debian 12

If relevant, including screenshots or a code block can be helpful in clarifying the issue.

No response

Please provide detailed steps to reproduce the issue.

No response

Originally created by @sartoricz on GitHub (Nov 8, 2024). ### Please verify that you have read and understood the guidelines. yes ### A clear and concise description of the issue. I deployed LXC container of OpenMediaVault and tried to add external disk. After searching some discussions I go to this: https://forum.openmediavault.org/index.php?thread/51217-trying-to-access-additional-drives-via-proxmox-with-lxc/ It seems that deploying OMV into LXC is not the preferred way and this script should be removed/replaced with VM deployment. ### What settings are you currently utilizing? Default Settings ### Which Linux distribution are you employing? Debian 12 ### If relevant, including screenshots or a code block can be helpful in clarifying the issue. _No response_ ### Please provide detailed steps to reproduce the issue. _No response_
saavagebueno added the not a script issue label 2025-11-20 04:42:39 -05:00
saavagebueno commented 2025-11-20 04:42:40 -05:00
Author
Owner
Copy Link

@Mellowlynx commented on GitHub (Nov 8, 2024):

It might be a good idea to remove it or add a notice of some sort that more knowledge and customizations (outside any support) is needed for it to work.
https://github.com/tteck/Proxmox/discussions/2554#discussioncomment-9095381

@Mellowlynx commented on GitHub (Nov 8, 2024): It might be a good idea to remove it or add a notice of some sort that more knowledge and customizations (outside any support) is needed for it to work. https://github.com/tteck/Proxmox/discussions/2554#discussioncomment-9095381
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label not a script issue
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#22
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?