Good Morning from my Robotics Lab! This is Shadow_8472, with a stubborn-project update. Let\u2019s get started!<\/p>\n\n\n\n
Nextcloud as a project comes with a lot of strings and hooks. Every time I sit down to work on it, the feature creep closes in: multiple volumes for speed and capacity, MariaDB container so SQLite doesn\u2019t choke serving clients, a pod for MariaDB to live in alongside Nextcloud, Redis for RAM caching (Out of my scope, but worth a mention), Ansible Vault for password management (automation tool I\u2019d need a month to learn), podman secrets, Philomena image board software \u2013 not to mention the volumes I learned about the other week! As noted in previously, the container I\u2019m using from docker.io can take care of itself, but it will work a lot better with even a few of these things.<\/p>\n\n\n\n
In my ideal configuration, all my containers\u2019 persistent data lives on GoldenOakLibry so my old, red laptop can take over on critical Podman containers when ButtonMash is booted to Debian for photo scanning duty. The big, hanging question then is if GoldenOakLibry\u2019s internal HDD\u2019s absolutely need to spin up to serve shares hosted on NAS volumes mounted from an external SSD.<\/p>\n<\/div>\n\n\n\n
HDD: Hard Disk Drive
NAS: Network Attached Storage
SSD: Solid State Drive<\/p>\n<\/div>\n<\/div>\n\n\n\n
My initial tests involved verifying that a drive could be mounted externally, then rebooting the NAS. I was expecting either a 1 or a 50 second wait, but instead I kept hitting \u201cStale file handle\u201d errors when I tried mounting the external share. My second round of trials a week or two later exhausted search pages worth of results to learn how NFS shares change a few invisible details when restarted. Either something wasn\u2019t ready when needed during boot, or my client just needs a while to refresh those details. It works in the long run, and external shares are not dependent on internal disk spinup. Time to move on.<\/p>\n\n\n\n
Having solved the last known problem, I started layering the bits I had solved while frustrated with the USB share. I prepared three Podman volumes: two for Nextcloud prioritizing high-capacity and speed, respectively, and one for an SQL database. A pod housing MariaDB (the SQL database) and Nextcloud containers mounts these volumes (!). Podman secrets safely injects the database password so MariaDB and Nextcloud can work together \u2013 not strictly necessary for my application, but a good habit to get in in case I go in the direction of creating images from existing containers. Once the cloud is running, I want to try adding an image board to view the pictures.<\/p>\n\n\n\n
(!) NFS \u2013as it turns out\u2013 does not appreciate a number of the acrobatics rootless Podman performs with Namespaces. I don\u2019t have the specifics memorized, but when Podman makes a container, the host\u2019s user ID is mapped to root within that container. Podman then assigns variations of the host\u2019s user ID to non-root users within the container as defined by a namespace. The NFS protocol wasn\u2019t designed with namespaces in mind. To NFS, it looks like you\u2019re trying to access another user\u2019s files \u2013 possibly without permission. While this reportedly doesn\u2019t stop rootless Podman from working well over NFS over normal circumstances, there are a bunch of search results talking about the snag when working with container images over NFS. Based off my experiences for this post, the same appears to hold true for volumes.<\/p>\n\n\n\n
As much as I wanted this to be the last installment, this issue is a post in and of itself, and I\u2019m getting burned out again over trying to come back to it. I\u2019ll try coming back to this in around a month or so.<\/p>\n\n\n\n
Have you successfully used Podman volumes over NFS? Please, do tell me all about it in the comments below or on my Socials<\/a>.<\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" Good Morning from my Robotics Lab! This is Shadow_8472, with a stubborn-project update. Let\u2019s get started! Nextcloud as a project comes with a lot of strings and hooks. Every time I sit down to work on it, the feature creep closes in: multiple volumes for speed and capacity, MariaDB container so SQLite doesn\u2019t choke serving … <\/p>\n