I tried several different CLI methods before I realized the PVE GUI method was the easiest and best solution for me. To mount a Turnkey Linux File Server CT within Proxmox:
After creating the TKLFS CT, go to Datacenter>[node name]>[TKLFS CT]>Resources>Add>Mount Point.
Here is my fio-status -a
root@r720xd1:~# fio-status -a
Found 1 ioMemory device in this system
Driver version: Driver not loaded
Fusion-io 1.65TB ioScale2, Product Number:F11-003-1T65-CS-0001, SN:1323G0577, FIO SN:1323G0577
Hello again Vladimir!
I hope you have been well in Moscow.
I had a power outage recently and when rebooting, my Fusion IO 2 driver would not load. My temps are still under control at 60C, so I decided to run the following build/modprobe as you suggest in your tutorial, but received...
Thank you for posting this, RobFantini. Your post allowed me to quickly solve a problem. I ran into this same 'namespacing permission denied' issue that was noted in my systemctl logs while creating a CT for a Syncthing server. Simply checking Options>Features>Nesting:ON took care of the problem!
I ran into this exact situation after completing a fresh install of PVE 5.4 (that I just downloaded) while testing another Fusion-IO Scale2 card I picked up. After installing PVE 5.4, I had kernel pve-4.15.18-12 and received:
Backing up initrd.img-4.15.18-12-pve to...
So after realizing I could not alter the ownership of the mounted directory from within the CT, I decided to try to mount a directory under the syncthing user home directory:
root@syncthing ~# su - syncthing
$ mkdir share
$ ls -hAl
Thank you for the suggestion. FYI: In PVE webUI: Datacenter>101 (syncthing)>Options>Features, I have nesting=1, mount=nfs,cifs. Aso, Unprivileged container= No.
From within TKL Syncthing CT (101) console:
root@syncthing ~# id syncthing
I am running PVE 5.4-11 on a r720xd configured with two containers. One is TKL File Server (100) which is configured with several cifs shares. Those shares are accessible and writable on numerous PCs on the LAN.
I have TKL Syncthing (101) installed as the second container. I am attempting to...
THANK YOU for posting this. I have been having a similar "bear" of a time trying to mount a TKL File Server contatiner share in a TKL Syncthing container. I have read that Proxmox bind mount page about a dozen times, and it never dawned on me that I needed to mount the share to the PVE host...
Can a PVE container access ZFS subvol of another container?
I am trying to setup TKL Syncthing on a r720xd server running Proxmox VE 5.4-11. I have the Syncthing CT installed and running. On the same PVE I also have a TKL File Server CT running.
On the r720xd, I have a ZFS pool created, which...
Thank you for posting this. It helped me three years later with my ZFS mount issue at boot! When I
zfs get overlay r720xd1
NAME PROPERTY VALUE SOURCE
r720xd1 overlay off default
I realized it was time to
zfs set overlay=on r720xd1
When I rebooted, my ZFS file system...
You are correct. My lack of proper cache file was the root of the issue causing problems with mounting of my ZFS pool at boot. I entered:
zpool set cachcefile=/etc/zfs/zpool.cache r720xd1
update-initramfs -k all -u
then rebooted. I noticed the root /r720xd1 was not mounted, but the...
I am running PVE 5.4-11 on a r720xd with a single CT for testing: TKL File Server.
I noticed while copying files from another NAS to the TKL File Server CT from a Win client on the LAN that the shares would strangely become unavailable. After a little digging and research in...
Thank you for requesting clarification on how to set default Scaling Mode on noVNC to Local Scaling. Now I have to stop myself from immediately clicking the settings gear>Scaling Mode option after every noVNC popup!!!
Thank you for passing this along. This has saved at least a...