Good Morning from my Robotics Lab! This is Shadow_8472 and today I am pressing on towards my very own Nextcloud deployment beyond a proof of concept. Let\u2019s get started!<\/p>\n\n\n\n
Last week, I learned that Rootless Podman comes with certain challenges when trying to access a network drive. ButtonMash\u2019s Rocky 8 Linux hard drive is tiny, so I don\u2019t want to use it for storage. That leaves my retired laptop, \u201cRedLaptop\u201d for the job.<\/p>\n\n\n\n
I use dedicated user accounts to isolate processes. The first order of business was to create a new account and log in through the Cockpit web interface. I had a bit of trouble when the underlying SSH couldn\u2019t connect because Debian doesn\u2019t like capital letters in its usernames, but the nonexistent, capital-containing username was flushed out while diagnosing user groups per advice on Discord. The account was additionally locked to prevent normal logins via password.<\/p>\n\n\n\n
I\u2019ve been developing a couple scripts for running Nextcloud on ButtonMash in a pod, so I copied them and the secrets directory (password storage) over to RedLaptop and tried them out. Errors galore! I downloaded the Nextcloud and MariaDB container images, but the older version of Podman (3.0.1 on Debian vs. 4.4.1 on Rocky 8) meant missing features \u2013 namely Podman secrets and mounting volumes on pod creation.<\/p>\n\n\n\n
The secrets were easy to revert. I just had to remove the –secret flags and reinstate the passwords in surrounded by quotation marks. Unlike best practices in later versions, volumes mounted nicely into their respective containers. I double checked one with<\/p>\n\n\n\n
podman inspect <container ID> | grep -i volume<\/pre>\n\n\n\nand found references to the correct volume.<\/p>\n\n\n\n
New Territory<\/h2>\n\n\n\n
At long last, I made it to the Nextcloud installation screen where I need to make an admin account. From here on, all I know comes from the little scouting I did way back by using an SQLite database hosted offered from the Nextcloud container as opposed to a more capable one.<\/p>\n\n\n\n
I got an error about failing to connect to the database. I found a username with a capitalization error and I didn\u2019t actually have a named database created within MariaDB\u2019s container. But even with both of those fixed, I kept getting kicked back to Nextcloud\u2019s create-an-admin screen.<\/p>\n\n\n\n
And here my research for the week runs out of time. MariaDB\u2019s log shows two errors I suspect to be the root issue:<\/p>\n\n\n\n
<timestamp> 0 [Warning] mariadbd: io_uring_queue_init() failed with errno 1
<timestamp> 0 [Warning] InnoDB: liburing disabled: falling back to innodb_use_native_aio=OFF<\/pre>\n\n\n\nTakeaway<\/h2>\n\n\n\n
I so want to be done with this project. That is all.<\/p>\n\n\n\n
Final Question<\/h2>\n\n\n\n
I am left without a solution for now. For all I know, it may be low RAM, which I\u2019m already maxed out on for my model of laptop \u2013 meaning I\u2019d need to start over again with something else. If anyone has any ideas, I\u2019d be happy to hear about them in the comments below or on my Socials<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"
Good Morning from my Robotics Lab! This is Shadow_8472 and today I am pressing on towards my very own Nextcloud deployment beyond a proof of concept. Let\u2019s get started! Preparing an Account Last week, I learned that Rootless Podman comes with certain challenges when trying to access a network drive. ButtonMash\u2019s Rocky 8 Linux hard … <\/p>\n