Vitaliy Filippov
09df74cfac
New store bug fixes: - Fix very slow OSD startup (hours) possible in unlucky cases - Fix incorrect garbage entry validation on start in some cases, preventing OSD startup - Fix small_write_throttling not functioning and either hanging or crashing OSDs - Fix "different fact_versions returned from subops" error possible with EC in some cases - Add a recovery option for the new store: skip_corrupted_meta_entries - Disable intent writes (even 4k) for hybrid OSDs by default for better write buffering Other changes: - Fix chmod/chown of a new empty VitastorFS root directory not working - Fix vitastor-dd treating all < 32k reads as always empty - Fix vitastor-disk always setting 32k csum_block_size for HDDs when checksums are enabled - Fix OSD missing PG state updates and PGs hanging in "starting" in rare cases - Fix a possible OSD crash with "map::at" message in rare cases when stopping a client - Fix a possible OSD crash on start when RDMA is available but fails to initialize - Fix removal and overwriting of totaled objects (objects with all corrupted copies) - Do not allow data_block_size < 8*bitmap_granularity - Remove RDMA ODP (On-Demand Paging) support - Update antietcd to 1.2.4 - Update Docker build to Debian Trixie - Add packages for AlmaLinux 10
2.3 KiB
Documentation → Installation → Dockerized Installation
Dockerized Installation
Vitastor may be installed in Docker/Podman. In such setups etcd, monitors and OSD all run in containers, but everything else looks as close as possible to a usual setup with packages:
- host network is used
- auto-start is implemented through udev and systemd
- logs are written to journald (not docker json log files)
- command-line wrapper scripts are installed to the host system to call vitastor-disk, vitastor-cli and others through the container
Such installations may be useful when it's impossible or inconvenient to install Vitastor from packages, for example, in exotic Linux distributions.
If you don't want just a simple containerized installation, you can also take a look at Vitastor Kubernetes operator: https://github.com/Antilles7227/vitastor-operator
Installing Containers
The instruction is very simple.
- Download a Docker image of the desired version:
docker pull vitalif/vitastor:v3.0.4 - Install scripts to the host system:
docker run --rm -it -v /etc:/host-etc -v /usr/bin:/host-bin vitalif/vitastor:v3.0.4 install.sh - Reload udev rules:
udevadm control --reload-rules
And you can return to Quick Start.
Upgrading Containers
First make sure to check the topic Upgrading Vitastor to figure out if you need any additional steps.
Then, to upgrade a containerized installation, you just need to change the VITASTOR_VERSION
option in /etc/vitastor/docker.conf and restart all Vitastor services:
systemctl restart vitastor.target
QEMU
Vitastor Docker image also contains QEMU, qemu-img and qemu-storage-daemon built with Vitastor support.
However, running QEMU in Docker is harder to setup and it depends on the used virtualization UI (OpenNebula, Proxmox and so on). Some of them also required patched Libvirt.
That's why containerized installation of Vitastor doesn't contain a ready-made QEMU setup and it's recommended to install QEMU from packages or build it manually.
fio
Vitastor Docker image also contains fio and installs a wrapper called vitastor-fio to use it from
the host system.