SoftwareMarbles / lazy

Hackable Coding Assistant
http://getlazy.org
MIT License
1 stars 0 forks source link

Move to intra-lazy API for managing engine containers #4

Closed ierceg closed 7 years ago

ierceg commented 7 years ago

Currently we give access to Docker host daemon to all engines. This is alright for now but presents two problems:

  1. Running lazy with custom engines will present a security hole (negligible in local, not so if running on say company's Docker cloud)
  2. We force all engines to "know" precisely how to use Docker daemon (which is mostly done through our engine helpers but should still be done by lazy)