Vitaliy Filippov
fe83825ead
Important fixes: - Disable RWF_ATOMIC by default because Linux incorrectly requires all atomic writes to be power-of-2-sized and length-aligned. Details: [use_atomic_flag](https://vitastor.io/en/docs/config/osd.html#use_atomic_flag) - Fix cross-pool snapshots not working at all - always reading old data after taking the snapshot - Fix level_placement (broken in 2.2.0) - Fix CAS write return values in the client library (broken in 2.4.4), also breaking unaligned writes in VitastorFS - Fix VitastorFS possibly losing some of intersecting parallel unaligned writes - Prevent possible reads of the old data during unfinished intent writes in the new store - Tests added for all of above problems to prevent future regressions Other fixes: - Allow to specify OSD tags and weights during prepare - Only clear the first block instead of whole OSD metadata and journal areas during vitastor-disk prepare - OSD anyway clears them on the first run - Fix vitastor-cli dd non-seekable detection and error status - Do not stop OSD on zero-copy tcp short send errors - these aren't a bug, but just caused by TCP client disconnections - Fix modify-osd not working after deleting the OSD configuration key from etcd - Fix regular antietcd websocket disconnections in OSD due to lack of WS_PONG responses to WS_PING - Reduce the number of allocated RDMA memory regions - Allow routed RoCE
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.1 - Install scripts to the host system:
docker run --rm -it -v /etc:/host-etc -v /usr/bin:/host-bin vitalif/vitastor:v3.0.1 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.