Docker Compose Wrapper • Hacker News Board

Re: Docker Compose Wrapper

#11

Post by pkaye » Sat, Mar 12, 2016, 2:18 PM UTC

skrebbel wrote: post #2

So this is a wrapper around a wrapper around a wrapper around linux containers? Is there any level at which this ever becomes user friendly?

Docker... it's wrappers all the way down...

Re: Docker Compose Wrapper

#12

Post by rmurri » Sat, Mar 12, 2016, 2:26 PM UTC

arez wrote: post #10

manojlds wrote: post #8

This might be more helpful - https://github.com/grammarly/rocker-compose

would you recommend it over docker-compose? Because I'm really searching for an alternative and it's in go, that's even better for me

I use https://github.com/michaelsauter/crane.

It has held up really well for me.

Re: Docker Compose Wrapper

#13

Post by yahyaheee » Sat, Mar 12, 2016, 3:20 PM UTC

What docker compose needs is a scheduler

Re: Docker Compose Wrapper

#14

Post by heitortsergent » Sat, Mar 12, 2016, 3:52 PM UTC

arez wrote: post #10

manojlds wrote: post #8

This might be more helpful - https://github.com/grammarly/rocker-compose

would you recommend it over docker-compose? Because I'm really searching for an alternative and it's in go, that's even better for me

There's also this one: https://github.com/azukiapp/azk

Re: Docker Compose Wrapper

#15

Post by ersoft » Sat, Mar 12, 2016, 3:54 PM UTC

arez wrote: post #10

manojlds wrote: post #8

This might be more helpful - https://github.com/grammarly/rocker-compose

would you recommend it over docker-compose? Because I'm really searching for an alternative and it's in go, that's even better for me

I'm using azk[0] for my development workflow with 30+ services defined in one Azkfile.js. It automatically setups http load balancers and dns services for you, no need for container linking.

[0] https://github.com/azukiapp/azk

Re: Docker Compose Wrapper

#16

Post by dominotw » Sat, Mar 12, 2016, 4:04 PM UTC

yahyaheee wrote: post #13

What docker compose needs is a scheduler

you can use it (with caveats) docker swarm.

Re: Docker Compose Wrapper

#17

Post by zimbatm » Sat, Mar 12, 2016, 4:06 PM UTC

Does any of these solutions give me back live-reload when developing web apps on OSX ?

As far as I know the code is uploaded into the container and only gets replaced when the image is re-created. At which point there are issues with private git dependencies because it can't access the SSH_AUTH_SOCK.

Re: Docker Compose Wrapper

#18

Post by frnhr » Sat, Mar 12, 2016, 4:10 PM UTC

Wrappers all the way down!

Re: Docker Compose Wrapper

#19

Post by athyuttamre » Sat, Mar 12, 2016, 4:44 PM UTC

zimbatm wrote: post #17

Does any of these solutions give me back live-reload when developing web apps on OSX ? As far as I know the code is uploaded into the container and only gets replaced when the image is re-created. At which point there are issues with private git dependencies because it can't access the SSH_AUTH_SOCK.

You could host a volume into your container containing the code base. Then use any standard live reloading library to make it work.

Re: Docker Compose Wrapper

#20

Post by sillypog » Sat, Mar 12, 2016, 6:03 PM UTC

athyuttamre wrote: post #19

zimbatm wrote: post #17

Does any of these solutions give me back live-reload when developing web apps on OSX ? As far as I know the code is uploaded into the container and only gets replaced when the image is re-created. At which point there are issues with private git dependencies because it can't access the SSH_AUTH_SOCK.

You could host a volume into your container containing the code base. Then use any standard live reloading library to make it work.

If the live reloading library relies on inotifywait, it won't detect changes made on the OSX side across the volume due to issues with Virtual Box. I made a utility that I run in my container while I'm developing to trigger these events: https://github.com/sillypog/inotify-proxy