Good Morning from my Robotics Lab! This is Shadow_8472, and today is another Nextcloud shot. Let\u2019s get started!<\/p>\n\n\n\n
It almost needs not an introduction at this point. I\u2019ve lost track of how long I\u2019ve been after a Nextcloud instance \u2013 and even the number of times I\u2019ve complained about the same. I\u2019ve demoed it using an integrated database, and I\u2019ve since gotten its container into a Podman pod. My task today is getting the paired MariaDB container to behave.<\/p>\n\n\n\n
Let\u2019s start with my first error. Nextcloud is starting for the first time and it\u2019s time to make an admin account.<\/p>\n\n\n\n
Failed to connect to the database: An exception occurred in the driver: SQLSTATE[HY000] [2002] No such file or directory<\/p>\n\n\n\n
The container has been launched with flags providing environment variables pointing Nextcloud at the database and specifying the username\/password to get in. I found someone having the exact same problem 4 years ago on Stack Overflow, and if I get user2880156\u2019s explanation, \u201clocalhost\u201d is not the same as spelling out a loopback IP address, like 127.0.0.1 [1]. While some networked applications don\u2019t care how they interact as server and client when on the same computer [namespace?], Nextcloud and MariaDB are not such a pair. It has something to do with types of network sockets, but I don\u2019t understand beyond that. What matters to me now is that replacing \u201clocalhost\u201d with \u201c127.0.0.1\u201d got me to my next error.<\/p>\n\n\n\n
MySQL username and\/or password not valid You need to enter details of an existing account.<\/p>\n\n\n\n
I\u2019ve checked my environment variables more times than I can count. The required usernames and passwords were copy-pasted between the respective environment variables. The best lead I have is that the container may be bugged. People online have reported success with manually creating the full permissions\/non-root account the database container is supposed to create on initial creation.<\/p>\n\n\n\n
This insight led me to seek a manual fix from within the pod \u2013 specifically from a MariaDB command line as mentioned in the container\u2019s documentation. After trying several different ways to modify a terminal command to run with Cockpit, I gave up, re-added a couple flags I was avoiding, and got the interface I was after rendered to both bash and Cockpit. I additionally split the command back into a separate script.<\/p>\n\n\n\n
The MariaDB command line is unlike any I\u2019ve used before. My first impressions are that commands are in all caps and variables are lower case. My final achievement before running out of time was to extract a list of user names (root, healthCheck, and databaseUser), where they\u2019ve logged in from (variations on locations within the pod), and a partial hexadecimal output of their passwords.<\/p>\n\n\n\n
Solving localhost vs 127.0.0.1 addresses has given me insight into Cockpit\u2019s curious behavior when remoting into to itself with localhost. Command line access to the database from within the pod is also huge.<\/p>\n\n\n\n
I\u2019m not taking bets, and I\u2019m afraid to ask, but what additional roadblocks should I expect?<\/p>\n\n\n\n
[1] akrea, et. all, \u201cnextcloud and mariadb (both) on docker: SQLSTATE[HY000] [2002] No such file or directory,\u201d stackoverflow.com<\/em> Mar. 10, 2019-Mar. 22, 2023. [Online]. Available:https:\/\/stackoverflow.com\/questions\/55088828\/nextcloud-and-mariadb-both-on-docker-sqlstatehy000-2002-no-such-file-or-d<\/a>. [Accessed Sept. 4, 2023].<\/p>\n","protected":false},"excerpt":{"rendered":" Good Morning from my Robotics Lab! This is Shadow_8472, and today is another Nextcloud shot. Let\u2019s get started! It almost needs not an introduction at this point. I\u2019ve lost track of how long I\u2019ve been after a Nextcloud instance \u2013 and even the number of times I\u2019ve complained about the same. I\u2019ve demoed it using … <\/p>\n