1 Overview
This section describes what is needed in terms of information to start building an application that works with Bubl sideloading. First, it explains why this information is needed, then each piece of information is described, and finally a full example is given.
The design is a result of these choices:
- Runs any containers
- Runs without data loss
- Runs stably
A major consequence of these design choices is that the container code runs in read-only mode, and only specific folders are mounted for:
- permanent storage
- temp storage
As a result, a fairly low-level container runtime is used, and the configuration is pre-made instead of dynamically generated.
An overview of a full example of all the info that is needed is given in a single table at the bottom of this page. See Full example.
At the highest level, the following is needed:
- Which containers
- Per container, the container source
- Per container, the container configuration
- Startup script