Fabio/qemu-arm
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: Readme

Browse source
This commit is contained in:
Kroese 2023-10-16 00:32:59 +02:00 committed by GitHub
parent 9eb9b15632
commit 17ac7bb4c1
1 changed files with 30 additions and 30 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

60
readme.md
View file

@ -24,19 +24,19 @@ Via `docker-compose.yml`
```yaml ```yaml
version: "3" version: "3"
services: services:
qemu: qemu:
container_name: qemu container_name: qemu
image: qemux/qemu-docker:latest image: qemux/qemu-docker:latest
environment: environment:
DISK_SIZE: "16G" DISK_SIZE: "16G"
BOOT: "https://dl-cdn.alpinelinux.org/alpine/v3.18/releases/x86_64/alpine-standard-3.18.2-x86_64.iso" BOOT: "https://dl-cdn.alpinelinux.org/alpine/v3.18/releases/x86_64/alpine-standard-3.18.2-x86_64.iso"
devices: devices:
- /dev/kvm - /dev/kvm
cap_add: cap_add:
- NET_ADMIN - NET_ADMIN
ports: ports:
- 22:22 - 22:22
restart: on-failure restart: on-failure
``` ```
Via `docker run` Via `docker run`
@ -53,7 +53,7 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
```yaml ```yaml
environment: environment:
BOOT: "https://dl-cdn.alpinelinux.org/alpine/v3.18/releases/x86_64/alpine-standard-3.18.2-x86_64.iso" BOOT: "https://dl-cdn.alpinelinux.org/alpine/v3.18/releases/x86_64/alpine-standard-3.18.2-x86_64.iso"
``` ```
It will be downloaded only once, during the initial run of the container. It will be downloaded only once, during the initial run of the container.
@ -64,7 +64,7 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
```yaml ```yaml
environment: environment:
DISK_SIZE: "256G" DISK_SIZE: "256G"
``` ```
This can also be used to resize the existing disk to a larger capacity without data loss. This can also be used to resize the existing disk to a larger capacity without data loss.
@ -75,7 +75,7 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
```yaml ```yaml
volumes: volumes:
- /home/user/data:/storage - /home/user/data:/storage
``` ```
Replace the example path `/home/user/data` with the desired storage folder. Replace the example path `/home/user/data` with the desired storage folder.
@ -86,8 +86,8 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
```yaml ```yaml
environment: environment:
CPU_CORES: "4" CPU_CORES: "4"
RAM_SIZE: "2048M" RAM_SIZE: "2048M"
``` ```
* ### How do I verify if my system supports KVM? * ### How do I verify if my system supports KVM?
@ -107,7 +107,7 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
```yaml ```yaml
environment: environment:
ARGUMENTS: "-drive file=/seed.iso,format=raw,if=virtio" ARGUMENTS: "-drive file=/seed.iso,format=raw,if=virtio"
``` ```
* ### How do I assign an individual IP address to the container? * ### How do I assign an individual IP address to the container?
@ -130,16 +130,16 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
```yaml ```yaml
services: services:
qemu: qemu:
container_name: qemu container_name: qemu
..<snip>.. ..<snip>..
networks: networks:
vlan: vlan:
ipv4_address: 192.168.0.100 ipv4_address: 192.168.0.100
networks: networks:
vlan: vlan:
external: true external: true
``` ```
An added benefit of this approach is that you won't have to perform any port mapping anymore since all ports will be exposed by default. An added benefit of this approach is that you won't have to perform any port mapping anymore since all ports will be exposed by default.
@ -154,11 +154,11 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
```yaml ```yaml
environment: environment:
DHCP: "Y" DHCP: "Y"
devices: devices:
- /dev/vhost-net - /dev/vhost-net
device_cgroup_rules: device_cgroup_rules:
- 'c *:* rwm' - 'c *:* rwm'
``` ```
Please note that even if you don't need DHCP, it's still recommended to enable this feature as it prevents NAT issues and increases performance by using a `macvtap` interface. Please note that even if you don't need DHCP, it's still recommended to enable this feature as it prevents NAT issues and increases performance by using a `macvtap` interface.