[SOLVED] (My solution sucks if you have a better one i would like to hear it) mnt media drive to host directly share to CTs, ended up locking myself out of CTs

Nemowashere

New Member
Oct 20, 2025
1
1
3
First attempt
I Have three containers set up ready to go just need to be able to feed the proper media into them.

CT 100 is plex pct set 100 -mp0 /mnt/pve/media11/,mp=/100/mnt/media
CT 101 is mstream pct set 101 -mp0 /mnt/pve/media11/,mp=/101/mnt/media
CT 103 is filemanager pct set 103 -mp0 /mnt/pve/media11/,mp=/103/mnt/mediatransfer

these are my three containers and the commands i used to get my mounts set up.
when i transferred all my files into the directory using CT 103 i could view two new folders plex & notplex from the other containers however from CT 100 and CT 101 i could not see any of the folders or loose files past that point. for example "/100/mnt/media/plex" would just appear empty same with "/101/mnt/media/notplex".

I also tried something called a recursive mount which is what google came up with which described a mount like this
lxc.mount.entry: /path/on/host /path/in/container none rbind,create=dir,optional 0 0
to add to my container config file. however the container either for whatever reason isnt using the config file i edited or ignored the mount i guess because the mount point was no accessible at all.

Second attempt
Welp I made it worse I nuked the system and started a fresh install and everything was working until i redone my mount points but at least i documented everything i done this time. because now my container logins dont work either.

#nuked proxmox fresh install
#Disabled enterprise repos added no subscription repos
#ran command
apt update && apt upgrade
#ran ve helper script (save time later) for plex
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/plex.sh)"
#yes
#3 Advanced settings
#container privliged
#set root passwd and verified
#set CT ID 100
#hostname plex
#disk size 8GB
#allocated CPU cores 2
#allocate ram in Mib 2048
#network bridge default vmbr0 Bridge
#IPv4 dhcp
#IPv6 auto
#APT-Cacher left blank
#MTU default 1500
#DNS Host
#Mac address left blank
#Vlan left blank
#SSH authorization key
#SSH authorization enabled
#enable Fuse
#enable verbose
#confirm Plex LXC creation
#write selections to config file
#approve VAAPI Passthrough
#verified access to plex web interface
#went back to Proxmox
#went to local(PVE)
#downloaded template
debian-13-standard
#create CT 101
arch: amd64
cores: 2
hostname: ****
memory: 2048
net0: name=eth0,bridge=vmbr0,firewall=1,hwaddr=BC:24:11:2F:1C:87,ip=dhcp,ip6=auto,typ>
ostype: debian
rootfs: local-lvm:vm-101-disk-0,size=8G
swap: 512
#template used
template used debian-13-standard
#entered CT 101
#ran command
apt update && apt upgrade
#shutdown CT 101
#cloned CT 101 to make CT 102
#ensured all containers were offline
#In webui initalized disk with gpt device /dev/nvme0n1
#In webui went to directory
#create directory
disk:/dev/nvme0n1
filesystem: etx4
Name: media11
add storage is checked
#path generated /mnt/pve/media11
#open host shell

#container config files to add lines to via command
nano /etc/pve/lxc/100.conf
nano /etc/pve/lxc/101.conf
nano /etc/pve/lxc/102.conf

#lines to add to contaier config file
#troublesome mnt point
mp0: /mnt/pve/media11,mp=/mnt/media11
#uid map: from uid 0 map 1005 uids (in the ct) to the range starting 100000 (on the host), so 0..1004 (ct) → 100000..101004 (host)
lxc.idmap = u 0 100000 1005
lxc.idmap = g 0 100000 1005
#we map 1 uid starting from uid 1005 onto 1005, so 1005 → 1005
lxc.idmap = u 1005 1005 1
lxc.idmap = g 1005 1005 1
#we map the rest of 65535 from 1006 upto 101006, so 1006..65535 → 101006..165535
lxc.idmap = u 1006 101006 64530
lxc.idmap = g 1006 101006 64530
#end of lines to add to CT config files

#add line to files via pve shell
nano /etc/subuid
nano /etc/subgid

#line to add
root:1005:1

#finale line in shell
chown -R 1005:1005 /mnt/pve/media11

#restart all containers
# Credentials to login to container no longer valid unable to enter container.

Please help Im not even sure what i done to create this new problem, also technically old problem still needs help too.

Third attempt
I wasn't finding much help and kind of got tired of running in circles trying to figure out how to do it the way i initially was attempting. So I elected to burn 50% of my systems resources to create a truenas VM.

I nuked the system again doing clean install.
spun up the truenas VM 4 cores and 8 GB of ram
I managed to pass through the physical 2TB Nvme drive to the VM and used that to create an NFS share (couldnt figure out how to get samba to work to save my life.)
Truenas eleminated the need for CT103 in my original plan. however using the remaining resources I did manage to create the other 4 CTs that I wanted though i had to minimize their resource pool since so much had to be given to the one VM. This also does limit a few side projects i wanted to do until a better solution can be found.

The obvious stuff
  • I do plan on increasing ram.
  • I do plan to get more drives so I can have live redundancies.
  • IF a lightweight alternative to truenas can't be found I will migrate it to a different machine when one can be acquired.
What I would like help with
  • I would like to find a better alternative (less resource intense) method than spinning up a truenas VM to share files to all my containers.
  • An easier method to upload multiple files whether it be to truenas or to whatever alternative is suggested.
  • Any kind of tips to help maximize what i can do with limited resources.
Thank you, in advance for any help or advise that you can provide.
 
Last edited:
  • Like
Reactions: used1d