Micro Service OS providing Transactional (Atomic) Updates upon a read-only btrfs root filesystem
Designed to host container workloads with automated administration & patching. Installing openSUSE MicroOS you get a quick, small environment for deploying Containers, or any other workload that benefits from Transactional Updates. As rolling release distribution the software is always up-to-date.
MicroOS offers an offline image. The main difference between the offline and self-install/raw images are that the offline image has an installer. Raw and self-install allows for customization via combustion or manually in the image after it is written to the disk. There is an option for a real-time kernel.
Try MicroOS in VMs running on either Xen or KVM. Using a Raspberry Pi or other System on Chip hardware may use the preconfigured image together with the Combustion functionality for the boot process. Both preconfigured and self-installed images are intended to be used with Combustion written to a USB, which is driven to allow configuration on any first boot, with the option for default password protected changes.Download
- Is not altered during runtime
- Will run the same artifacts consistently on every boot
- Eliminates efforts in configuring individual instances during runtime
- Can be rolled out easily repeatedly with predictable outcome
- Automated recovery from faulty updates
By using btrfs with snapshots MicroOS uses a very space
efficient way to store the file system’s history. All the configuration
/etc are part of the snapshot and the rollback.
- No new package format is needed, use standard openSUSE RPMs
- No size limitation, neither for partitions nor the operating system
- Easy to enhance
MicroOS is an Immutable OS, rollback is simple
- Immutable: No changes on disk
- Rollback by rebooting to an old BTRFS snapshot
- Get your updates via HTTPS
- Packages and repositories are signed by our build system
- Packages are verified
- No updates are done in case of dependency conflicts
- No waste of space: Filesystem snapshots get deleted in case of unsuccessful updates
Applications are installed in containers rather than the root filesystem:
- Isolated from the core filesystem
- Reduced ability for malicious applications to compromise the system
- New installation without reboot
- Update in atomic way possible (create new, kill old)
- Easy rollback
Debugging Toolbox Container
- Launches privileged container
- Root filesystem available below
- zypper to install the necessary tools, available without reboot
- Persistent between usages
Requisitos de Sistema Recomendados
- 2 GB de memória de sistema (RAM): 1GB physical RAM + additional memory for your workload
- / (root) partition: 5GB available disk space
- /var partition: 5GB available disk space
- 2 GB de memória de sistema (RAM): 2GB physical RAM + additional memory for your workload
- / (root) partition: 20GB available disk space
- /var partition: 40GB available disk space
Verificar a Sua Transferência Antes de Usar
Muitas aplicações podem verificar a soma de verificação (checksum) de uma transferência. Verificar a sua transferência pode ser importante para ter realmente a certeza que recebeu o ficheiro ISO que pretendia descarregar e não uma versão qualquer corrompida.
Para cada ISO, oferecemos um ficheiro com a soma de verificação correspondente à soma SHA256.
Para segurança extra, pode utilizar GPG para verificar quem assinou esses ficheiros .sha256.
Para mais ajuda sobre como verificar a sua transferência por favor leia Ajuda Soma de Verificação