I've Got A Use Case for Runnin' Kubs

Get it? My last two blog titles...

Docker Docker Give Me The News /

I've Got a Use Case for Runnin' Kubs

Yeah, I know it's awful. But anyway

If you've been keeping up with this blog, you'll know that last time I checked in (yesterday, in fact!) I spent hours trying to get Oqtane to run in a Docker container, failed most of the day, and then in the end: triumph! Well, sorta. I still hadn't hooked it up to a database of any sort, but, it worked!

Today was more of the same: I spent some time getting postgreSQL running in a container, got that all set, wrote up a Docker Compose file to spin up both my db and Oqtane, and... it failed.

Hours later, I finally narrowed down the problem to one source: the Docker image. Shocking, innit, that a guy who has only been working with Docker for less than a week would screw up a Dockerfile.

I tried, and tried, and tried more. Google, try. Google, try. AI, try. When my friend suggested it could be permissions issues, I thought he was crazy! Or was he?

Turns out, there's one line that I copied in from a tutorial that sets the USER to an $APP_UID, and naturally because it makes my life harder, that user wasn't blessed with write permissions in the Docker universe.

Also naturally, this was one of the last lines I inspected in the code. I just kinda, glanced over it, repeatedly all day. The moral of the story? Just like my hard lesson in learning to read the docs carefully, I have a rule that I broke today: if you're copying in code, even from official tutorials or auto-genned code, *know what each line is doing.*

With all that said, I've now got a Docker Compose file to spin up three containers on one network: an Oqtane instance, a postgreSQL database, and a db admin instance, and it all happens seamlessly: Docker is pretty damned neat.