This message was deleted.

well to do a multi container app you could do a compose based app or you could do full kubernetes. you don’t need all of kubernetes if you are using compose.

can a compose setup be booted at startup ? or would it require a command the engineers run to start it up

[docker|nerdctl] compose up

now starting when the laptop starts gets sticky as you need ot start the container hosting stuff as well (Rancher Desktop in this case) so timing would be a mess

so you would recommend just compose route for now, avoid kubernetes ? my experience with kubernetes is limited (primarily, i have interacted with k8s as a large thing to allocate address blocks for)

if you don’t need all that k8s brings and given you are single node it adds a lot of domain knowledge that doesn’t sound like you need

ok, will try this compose route. any pointers to resources on writing a compose file, like a tutorial?

hmm.. blocked at work.

hah well don’t look at archive.is or 12ft.io as ways to handle that.

thank you'

and lots of exmaple app+db on github as well.

it is a forcing function i am sure.. forcing the <large> population of users to conform to the corp direction set to use rancher-desktop and block access to docker registry

well docker and docker desktop are not an equivalent. lots of helpful data in their docs site for folks given they authored most of the implementations before they went into OSS stewardship. tons of examples out there on github and other vendor agnostic systems to get you going on compose. and there is the primary upstream as well https://github.com/compose-spec

thank you, i really appreciate it