kentonv changed the topic of #sandstorm to: Welcome to #sandstorm: home of all things sandstorm.io. Say hi! | Have a question but no one is here? Try asking in the discussion group: https://groups.google.com/group/sandstorm-dev | Public logs at https://botbot.me/freenode/sandstorm/
pie__ has quit [Ping timeout: 244 seconds]
ogres has joined #sandstorm
_whitelogger has joined #sandstorm
nicoo has quit [Ping timeout: 256 seconds]
nicoo has joined #sandstorm
ogres has quit [Quit: Connection closed for inactivity]
pie__ has joined #sandstorm
<xet7> dkcd: Firecracker manages KVM VMs with REST API. Sandstorm uses cgroups like Docker on same kernel. Docker keeps containers running all the time. Sandstorm keeps containers running only when they are in use, being most RAM friendly. Sandstorm if full integrated platform with SSO login to all apps. Docker and Firecracker are just low-level tools, not a platform.
<xet7> dckc: ^
<dckc> thanks.
<dckc> though... I'm more interested in the security properties.
<dckc> sandstorm has the property that all access has to be explicitly granted.
<dckc> (I think)
<dckc> in Docker, a container gets a certain amount of access by default and you have to jump through hoops to constrain it
<xet7> dckc: What kind of security properties?
<xet7> Sandstorm grains have many more cgroups/kernel privileges turned off than Docker, so security issues that affect Docker don't usually affect Sandstorm grains