Piotr
Piotr
@fclaudiopalmeira you shouldn't have to install `libvirt`, etc. to be able to run Docker Desktop. `qemu` should should get installed automatically since we declare it as a dependency. I suppose...
@disdi - did you make sure your user is allowed to use KVM (https://docs.docker.com/desktop/linux/install/#kvm-virtualization-support)? also could you paste the contents of your `~/.docker/desktop/log/host/com.docker.driver.amd64-linux.*.log`, or even better a full diagnostic (https://docs.docker.com/desktop/linux/troubleshoot/#in-app-diagnostics)?
@disdi - thanks. Based on the VM driver logs it looks like your `qemu` installation is missing (or can't access) a dependency: com.docker.driver.amd64-linux.stderr: qemu-system-x86_64: error while loading shared libraries: libxenctrl.so.4.11:...
Thanks for reporting this issue :) We'll investigate and get back to you as soon as we have a fix for this.
hi @nicekiwi, sorry for the long wait, we've got a candidate fix for this issue. Here - https://desktop-stage.docker.com/linux/main/amd64/78870/docker-desktop-4.8.0-amd64.deb - you will find a dev build with the fix in it....
@cardonator it will be released in 4.9, which is scheduled to come out at the beginning of June
@DonRichards there are no RCs yet, but, if you are willing, you can give the latest dev build a go: * https://desktop-stage.docker.com/linux/main/amd64/79987/docker-desktop-4.9.0-amd64.deb * https://desktop-stage.docker.com/linux/main/amd64/79987/docker-desktop-4.9.0-x86_64.rpm * https://desktop-stage.docker.com/linux/main/amd64/79987/docker-desktop-4.9.0-x86_64.pkg.tar.zst
@cardonator and @DonRichards, the weird permissions are an effect of how file sharing is implemented. Basically Docker Desktop is supposed to be able to run without elevated privileges, so you...
@Kowiste, sorry for the inconvenience and thanks for providing info on the error you are seeing. What I am pretty sure is going on is that files in the folder...
@Kowiste - this is a bit more worrying. I was able to reproduce the issue and work around it by creating the `mariadb` folder, before running compose: docker compose down...