Running engine: engine linux/qemu failed to run: running VM: running virtiofsd for /home: signal: bad system call (core dumped)

Docker Desktop
, ,
1

Welcome to Docker Extensions!

Hello every one.
I am using docker 27.5.0, build a187fa5 version now I have faced to unexpected problem.
When I try to run docker after afew minutes it engine stopped and give me this error:
running engine: engine linux/qemu failed to run: running VM: running virtiofsd for /home: signal: bad system call (core dumped)

OS: Ubuntu 22
RAM: 16GB
VM box tpye: Virtual box

Screenshot from 2025-01-19 15-05-37
Screenshot from 2025-01-19 15-05-37737×595 54.4 KB

2

Do you know what Docker Extensions are?

Docker Desktop runs a virtual machine even on Linux. If you want to install it in an existing virtual machine, you need to enable nested virtualization.

I’m not familiar with the virtiofsd error message. but if you got that, I assume nested virtualization is enabled and the problem is with mounting your home so containers can access it. There is an existing issue on GitHub

It could be a bug in the version you are using.

That could be the Docker CE version, but according to the documentation and my Docker Desktop, the latest Docker DEsktop has only v27.4, not v27.5.

Please, share the output of docker version

And don’t forget to check the general system requirements: https://docs.docker.com/desktop/setup/install/linux/#general-system-requirements

3

I can see how it could be a problem, if the vbox vm mounts a host folder into a vm folder, and this vm folder is used as a bind for a container in Docker Desktop.

As this post doesn’t seem to belong in the “Docker Desktop Extensions” category, I moved the post to the “Docker Desktop” category, and added the lables “virtualbox”, “linux-vm” and “ubuntu”.

1 Like
4

No brother I installed Oracle VM box on my host Ubuntu in my home directory and the docker is also installed on host (Ubuntu). This is the problem that occured in my host there. And I don’t wanna install docker on my VM.

General information:

[Mon Jan 20][11:34:59]:~$ docker version
Client: Docker Engine - Community
 Version:           27.5.0
 API version:       1.47
 Go version:        go1.22.10
 Git commit:        a187fa5
 Built:             Mon Jan 13 15:24:49 2025
 OS/Arch:           linux/amd64
 Context:           desktop-linux

Server: Docker Desktop 4.36.0 (175267)
 Engine:
  Version:          27.3.1
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.7
  Git commit:       41ca978
  Built:            Fri Sep 20 11:41:11 2024
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.21
  GitCommit:        472731909fa34bd7bc9c087e4c27943f9835f111
 runc:
  Version:          1.1.13
  GitCommit:        v1.1.13-0-g58aa920
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
5

No I don’t no if give little information

6

Try using a matching client version. The version you shared was the client version, but you are using v27.3.1 in Docker Desktop. The Docker Desktop version could be updated too. So my advice: Update Docker desktop to the latest version (download the latest which should override the current version) and if it still doesn’t work, install the same client version. 27.5.0 is the latest in Docker CE, but not in Docker Desktop’s Docker CE. Small difference shouldn’t be a problem, but Docker Desktop is special enough to be more careful with the versions.

You can find lots of information just by searching for “Docker extensions” on Google or by reading topics in the category, so I would not start a detailed explanation. I think “extension” should be quite clear :slight_smile: But you can call it plugin.

7

This topic was automatically closed 10 days after the last reply. New replies are no longer allowed.