107
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
Newest
Oldest
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 DuongK
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!