There is plenty of online discourse about mounting and accessing a network folder from an unprivileged ProxMox LXC. This is not one of them.
I am attempting to make a specific folder on the unprivileged LXC write-accessible to my Windows 10 daily driver via Network Share folder. In particular, the folder is the /opt/paperless/consume on unprivileged LXC.
I am on 7.4-17.
For those unaware, there is a feature of paperless-ngx where you can specify a folder that the service monitors (default above), and when a file is present, it indexes it, ocrs it, copies it to its permanent home in the paperless-ngx data folder, and then deletes the original file. I'd like to be able to drop select files in there throughout my day into a Windows folder trusting that the above actions happen.
My only real constraint is that I want to avoid making any changes to the PVE host because I'm running a hyper-converged HA cluster across "vanilla" hosts that may grow and I don't want to start syncing host configuration.
This debian paperless-ngx LXC container was generated from one of u/tteckster's amazing helper scripts (many kudos and much karma to you!) in case that's relevant.
Here's what I've tried (Thank God for Quick and Easy Snapshots and rollbacks in ProxMox):
TL;DR What is the simplest and quickest way (without changes to PVE host) to make a folder on an unprivileged LXC write-accessible in Windows explorer.
I am attempting to make a specific folder on the unprivileged LXC write-accessible to my Windows 10 daily driver via Network Share folder. In particular, the folder is the /opt/paperless/consume on unprivileged LXC.
I am on 7.4-17.
For those unaware, there is a feature of paperless-ngx where you can specify a folder that the service monitors (default above), and when a file is present, it indexes it, ocrs it, copies it to its permanent home in the paperless-ngx data folder, and then deletes the original file. I'd like to be able to drop select files in there throughout my day into a Windows folder trusting that the above actions happen.
My only real constraint is that I want to avoid making any changes to the PVE host because I'm running a hyper-converged HA cluster across "vanilla" hosts that may grow and I don't want to start syncing host configuration.
This debian paperless-ngx LXC container was generated from one of u/tteckster's amazing helper scripts (many kudos and much karma to you!) in case that's relevant.
Here's what I've tried (Thank God for Quick and Easy Snapshots and rollbacks in ProxMox):
- Looked into syncthing, duplicati, rsync. Decided to attempt install syncthing on the container, but even though the service ran and I could curl the GUI from within the container, I could not access it in my browser on my Windows machine. Troubleshot for a bit (firewall, etc.). Abandoned.
- Began looking into FOSS for sftp clients and services that could run on windows and integrate a remote sFtp into explorer (WinFSP). Paused on this.
- Installed Samba using apt and configured following this guide. Came really close. Could access the folder. Could see and open files already created on the LXC host. Could not create, copy, or save changes from Windows. Windows threw a permissions error. Troubleshot for a while (mostly focused on sambauser permissions on the LXC) Abandoned.
- Attempted to apt install nfs-kernel-server. It errored out and I troubleshot finally arriving at "of course a container can't run a kernel module like nfs-kernel-server, maybe try a a user space NFS server like Ganesha-NFS?" (I had no idea; the concepts of kernel-space and user-space had not existed in my mind prior). Abandoned.
- Diving deeper into the Windows + sFTP option
- Trying Samba again with fresh eyes and troubleshooting the write permission issue.
- Starting fresh and using docker to compose a paperless+syncthing container.
TL;DR What is the simplest and quickest way (without changes to PVE host) to make a folder on an unprivileged LXC write-accessible in Windows explorer.
