https://github.com/mysmartspaces/container-qemu

https://github.com/mysmartspaces/container-qemu

Last synced: 3 days ago
JSON representation

• Host: GitHub
• URL: https://github.com/mysmartspaces/container-qemu
• Owner: mysmartspaces
• Created: 2024-01-12T21:31:58.000Z (10 months ago)
• Default Branch: master
• Last Pushed: 2024-01-12T21:32:08.000Z (10 months ago)
• Last Synced: 2024-01-13T20:50:56.741Z (10 months ago)
• Language: Shell
• Size: 26.4 KB
• Stars: 0
• Watchers: 2
• Forks: 0
• Open Issues: 0
• Metadata Files:
  • Readme: readme.md

Awesome Lists containing this project

README

        
# qemu-docker

[![Test](https://github.com/joshkunz/qemu-docker/actions/workflows/test.yaml/badge.svg)](https://github.com/joshkunz/qemu-docker/actions/workflows/test.yaml)

This repository contains a Docker container for running x86\_64 virtual

machines using QEMU. It uses high-performance QEMU options

(KVM, and TAP network driver).

Docker Hub: [jkz0/qemu](https://hub.docker.com/r/jkz0/qemu)

## Using the container

Via `docker run`:

```bash

$ docker run --rm -it \

    --device=/dev/kvm:/dev/kvm --device=/dev/net/tun:/dev/net/tun \

    --cap-add NET_ADMIN -v $VM_IMAGE_FILE:/image \

    jkz0/qemu:latest

```

Via `docker-compose.yml`:

```yaml

version: "3"

services:

    vm:

        image: jkz0/qemu:latest

        cap_add:

            - NET_ADMIN

        devices:

            - /dev/net/tun

            - /dev/kvm

        volumes:

            - ${VM_IMAGE:?VM image must be supplied}:/image

        restart: always

```

## Tips 

* VM networking is configured via DHCP, make sure to enable DHCP in your

  VM image. VMs will use the IP address of the container.

* You can quit the VM (when attached to the container) by entering the special

  key sequence `C-a x`. Killing the docker container will also shut down the

  VM.

## Caveat Emptor

* Only x86\_64 supported new. PRs to support other architectures welcome,

  though I imagine 99% of use-cases will be x86\_64.

* VMs will not be able to resolve container-names on user-defined bridges.

  This is due to the way Docker's "Embedded DNS" server works. VMs can still

  connect to other containers on the same bridge using IP addresses.