221
Support docker-compose
under review
K
Kai Marshland
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
docker-compose up
Log In
Activity Feed
Sort by
M
Miguel VC
please, we need docker-compose
d
dylan
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?
s
service
Please! At least some basic functions like to run services:
version: '3'
services:
redis:
container_name: redis
image: 'redis:6.2.1-alpine'
command: redis-server --requirepass ***
ports:
- '6379:6379'
Anurag Goel
under review
Anurag Goel
How about starting with
render.yaml
now? 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 all
docker-compose options render.yaml
runs the risk of becoming much more complex.K
Kai Marshland
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.
Anurag Goel
Kai Marshland: Interesting thought. Maybe we
should
create a docker-compose.yaml -> render.yaml convertor as a live utility in the docs. cc Adrian DuongD
Daniel Trostli
Anurag Goel: I like this idea!
L
Lloyd Chang
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.
Whereas
docker-compose.yaml
→ render.yaml
seems like an additional layer of abstraction with edge cases and room for bugs.While
render.yaml
is 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 docker-compose.yaml
and Kubernetes.Open question: Would it be more effective and more efficient to directly translate from
docker-compose.yaml
to Kubernetes via https://kompose.io/ ?Thank you.
Anurag Goel
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.
L
Lloyd Chang
Thanks Anurag Goel; got it. Render Cloud seems well-situated as an UX-Driven PaaS
plus
the potential opportunities of an Open-Core Business Model via its render.yaml
abstraction layer.P
Pathikrit Bhowmick
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?
K
Kai Marshland
Related to, but distinct from https://feedback.render.com/features/p/support-infrastructure-as-code
r
redwrasse
I'm a new Render user, surprised I even have to bother converting my docker-compose.yaml to render.yaml!