Has anyone had trouble with Kompose messing up the conversion from Docker Compose files to Kubernetes manifests? I recently tried converting a Compose for ForgeJo, and it bizarrely turned the localtime bind mount into a full hex dump of the actual localtime binary. Am I using it incorrectly, or is this a common issue?
3 Answers
I tried the ForgeJo example Docker Compose and it worked perfectly for me! Maybe there was a small mistake in your setup?
I've had no problems with it on a few occasions, but if your project wasn't initially designed for containers, it can feel like trying to force a round peg into a square hole. You might have to change some things in your app or compromise on cloud-native practices.
You could use the Helm chart to install ForgeJo. Check it out here: artifacthub.io/packages/helm/forgejo-helm/forgejo. If you’re not keen on delving into all the Kubernetes details, just installing the chart with some example values should get you up and running pretty easily.
That site looks like it’ll be a huge help! I'm trying to figure out how to document everything in my home lab repository. Installing via Helm feels different from writing a Docker Compose file since I'm just typing commands instead of creating a file to push to GitHub.
I probably messed it up! I have zero experience with Kubernetes, so it's a bit daunting! LOL