I often write my apps with docker-compose to specify all the docker options. I would render to be able to read my docker-compose file, create all the services, and appropriately coordinate between them, as if I had simply run
This would be a huge plus for Render IMHO. For example, deploying a library such as Pelias (https://github.com/pelias/docker) turns out to be extremely tedious given the current approach of translating a compose file to a render.yaml
please, we need docker-compose
please, we need docker-compose
Having issues converting my docker-compose to render.yaml files and Dockerfiles. Would love to be able to use render for our core app deployments which is a collection of 5 services. What is the best way to go about doing this since this post is 4 years old now and I don't believe docker-compose is supported yet?
Please! At least some basic functions like to run services:
command: redis-server --requirepass ***
marked this post as
How about starting with
render.yamlnow? docker-compose assumes certain options that aren't directly translatable to Render (yet): for example, private networks, certain Docker runtime options, and multiple volumes for a container. If we tried to support
render.yamlruns the risk of becoming much more complex.
Anurag Goel: Maybe it could auto-generate a render.yaml from the docker-compose.yml? A big piece of this is the friction of deployment. I totally get that some features aren't supported (and some may never be), and I'm fine if it warns/doesn't work with those, but I'd like to be able to click create and not think about infrastructure ever again.
Out of the four most common docker-compose commands I use (build, command, ports, and volumes), render supports three already.
Kai Marshland: Interesting thought. Maybe we
shouldcreate a docker-compose.yaml -> render.yaml convertor as a live utility in the docs. cc Adrian Duong
Anurag Goel: I like this idea!
Hi Anurag Goel, Adrian Duong, Kai Marshland, Daniel Trostli,
In this specific situation...
Have you considered leveraging https://kompose.io/ ?
My high-level understanding is that Render already runs Kubernetes behind the scenes.
render.yamlseems like an additional layer of abstraction with edge cases and room for bugs.
render.yamlis great for new Render Blueprints...
It may not be a good fit for purpose in this specific situation by introducing an intermediary layer (
render.yaml) in between
Open question: Would it be more effective and more efficient to directly translate from
docker-compose.yamlto Kubernetes via https://kompose.io/ ?
Lloyd Chang: Render does a lot more on top to run services in Kubernetes, so k8s YAMLs don't match cleanly to our systems. We'd still prefer to create a render.yaml once we get to this.
Thanks Anurag Goel; got it. Render Cloud seems well-situated as an UX-Driven PaaS
plusthe potential opportunities of an Open-Core Business Model via its
Anurag Goel: I am migrating my services to render and I have this dockerfile: https://docs.visionect.com/_downloads/cda94dc639573626dadb9a3c907a429f/docker-compose.yml
Can you help me translate to a render.yml file?
I'm a new Render user, surprised I even have to bother converting my docker-compose.yaml to render.yaml!