Docker Development
Barbara OS supports docker containers, to deploy and run them, Barbara OS use docker-compose under the hood to orchestrate everything.
Barbara OS requires that docker app files and folders be structured concretely inside the ZIP file that should be used to upload the app to Barbara Panel.
- Docker-compose YAML file can only be named docker-compose.yaml or docker-compose.yml, otherwise, docker installation will fail.
- All persistence files/folders must be placed inside a “persist” folder in the ZIP root folder, any other file/folder could be used to build containers but will be replaced/deleted if the docker app is updated
- Native docker volumes are not yet allowed
- Only bind mounts are allowed, but only if that mount point (host side) contains “./persist/”, “./appconfig” or “./sys/” at the beginning.
- Privileged containers are not allowed
- Admin-related capabilities are not allowed
- Devices access must be declared explicitly
This is a docker-compose.yaml example:
version: '3.8'
services:
logApp:
build: .
restart: "unless-stopped"
volumes:
- "./appconfig/:/appconfig/"
- "./sys/:/sys/"
devices:
- /dev/gpiomem:/dev/gpiomemDocker Apps examples
The following repositories contain docker application examples:
Every Docker example contains an appconfig sample to be able to interact with the Docker from Barbara Panel
Barbara OS Docker tips
- You must be aware of the platform of the Barbara OS device, and the Docker images platform/architecture compatibility, some deployments can run on a PC (x86_64) but not inside a Raspberry Pi 3 (armv7)
- Here are some Barbara OS groups gid, needed in some cases by Docker apps to get access to some devices:
- gpio – 10000
- spi – 117
- i2c – 115
- kmem – 9
- If your docker image needs specific permissions for your persistence folder, please contact Barbara’s support team to help you.