3 ms·
Sandstorm actually self-containerizes. The installer unpacks a bundle under /opt/sandstorm which, when executed, runs itself in a container (Linux namespace) an
by kentonv 11y ago
Sandstorm actually self-containerizes. The installer unpacks a bundle under /opt/sandstorm which, when executed, runs itself in a container (Linux namespace) and mostly avoids interacting with the rest of the system. It also (with your permission) auto-updates itself within 24 hours of any release with near-zero downtime.
I know that Docker-izing it could be more comfortable for people who are already familiar with launching Docker images, and similarly Debian packages would be more comfortable to long-time Debian users, etc. But, these other distribution mechanisms would have significant technical disadvantages compared to what we have (and what we are building), while adding some significant maintenance cost for us. So we've decided not to pursue them for now. That said, it might make more sense when we have a "stable release".
Regarding Synology, they actually sent us a test unit that we plan to play with at some point... so much to do, so little time.
- jimmcslim 11y ago> Sandstorm actually self-containerizes. Ok, that's interesting... so hopefully it wouldn't conflict with my Docker install and its containers at all (other than port numbers I suppose).
- kentonv 11y agoCorrect. Other than port numbers, Sandstorm should have no interaction with anything else on the system, including Docker. (Please file a bug if you find otherwise. :) )