3 ms·

I'm struggling to see the advantage of this? Surely either running the entire thing in the container and just running the command using subprocess would achieve

• takee 11y ago
  Or, if you have docked installed on a system anyway why not just use docker-py (docker's python bindings) directly to run stuff in containers?
  • noajshu 11y ago
    you can! I found it difficult to work with and decided to make something new after reading this post: http://blog.bordage.pro/avoid-docker-py/ http://blog.bordage.pro/avoid-docker-py/ It's a few years old but I think docker-py still needs some love for it to really shine.
• rco8786 11y ago
  I can see it being useful for building up a testing environment/framework
  • noajshu 11y ago
    Absolutely, we use it especially because our servers are linux and our personal machines are mac. Most of our app is not containerized but sidomo helps us make the 'fiddly bits' (e.g., ffmpeg) super portable.
• noajshu 11y ago
  Hi, I'm one of the devs. That's totally true, but it means the python app can only run in the same container as the process. I thought there were essentially 2 really cool features of this: you don't have to clean up after your (sub)processes and your docker daemon could be running remotely. (e.g., you could distribute tasks to a bunch of servers running your containers)