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

README

Browse source 
README
This commit is contained in:
Kroese 2023-04-23 03:38:03 +02:00 committed by GitHub
commit 337b802897
1 changed files with 26 additions and 44 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

70
readme.md
View file

@ -58,55 +58,38 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
## FAQ
* ### How do I change the bootdisk? ###
* ### How do I specify the boot disk?
You can modify the `BOOT` setting to specify the URL of any ISO image:
You can modify the `BOOT` environment variable in your compose file to specify the URL of an ISO image:
```
environment:
BOOT: "http://www.example.com/image.iso"
```
It will be downloaded only once, during the first run of the container.
It will be downloaded only once, during the initial run of the container.
* ### How do I change the size of the data disk? ###
* ### How do I change the size of the data disk?
By default it is 16GB, but to increase it you can modify the `DISK_SIZE` setting in your compose file:
To expand the default size of 16 GB, locate the `DISK_SIZE` setting in your compose file and modify it to your preferred capacity:
```
environment:
DISK_SIZE: "16G"
```
To resize the disk to a capacity of 8 terabyte you would use a value of `"8T"` for example.
* ### How do I change the location of the data disk?
* ### How do I change the location of the data disk? ###
By default it resides inside a docker volume, but to store it somewhere else you can add these lines to your compose file:
To change the data disk's location from the default docker volume, include the following bind mount in your compose file and replace the path `/home/user/data` with the desired storage folder:
```
volumes:
- /home/user/data:/storage
```
Just replace `/home/user/data` with the path to the folder you want to use for storage.
* ### How can I increase the allocated amount of CPU/RAM?
* ### How do I change the space reserved by the data disk? ###
By default the total space for the disk is reserved in advance. If you want to only reserve the space that is actually used by the disk, add these lines:
```
environment:
ALLOCATE: "N"
```
This might lower performance a bit, since the image file will need to grow every time new data is added to it.
* ### How do I change the amount of CPU/RAM? ###
By default a single core and 512MB of RAM is allocated to the container.
To increase this you can add the following environment variabeles:
By default, a single core and 512MB of RAM is allocated to the container. To increase this, add the following environment variables:
```
environment:
@ -114,24 +97,22 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
RAM_SIZE: "2048M"
```
* ### How do I check if my system supports KVM?
* ### How can I verify if my system supports KVM?
To check if your system supports KVM run these commands:
To verify if your system supports KVM, run the following commands:
```
sudo apt install cpu-checker
sudo kvm-ok
```
If `kvm-ok` returns an error stating KVM acceleration cannot be used, you may need to change your BIOS settings.
If you receive an error from `kvm-ok` indicating that KVM acceleration can't be used, check your BIOS settings.
* ### How do I give the container its own IP address?
* ### How do I assign an individual IP address to the container?
By default the container uses bridge networking, and uses the same IP as the docker host.
By default the container uses bridge networking, and uses the same IP address as the docker host.
If you want to give it a seperate IP address, create a macvlan network.
For example:
If you want to assign a unique IP address to the container, you can create a macvlan network by running the following command:
```
$ docker network create -d macvlan \
@ -140,31 +121,32 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
--ip-range=192.168.0.100/28 \
-o parent=eth0 vlan
```
Modify these values to match your local subnet.
Be sure to modify the values to match your local subnet.
Now change the containers configuration in your compose file:
Once you have created the network, modify the container's configuration in your compose file as follows:
```
networks:
vlan:
ipv4_address: 192.168.0.100
```
And add the network to the very bottom of your compose file:
Finally, add the network to the bottom of your compose file:
```
networks:
vlan:
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.
This also has the advantage that you don't need to do any portmapping anymore, because all ports will be fully exposed this way.
Please note that this IP address won't be accessible from the Docker host due to the design of macvlan, which doesn't permit communication between the two. If this is a concern, there are some solutions available, but they go beyond the scope of this FAQ.
NOTE: You will not be able to reach this IP from the Docker host, as macvlan does not allow communication between those two. There are some ways to fix that if necessary, but they go beyond the scope of this FAQ.
* ### How can the container acquire an IP address via DHCP?
* ### How can the container get an IP address via DHCP? ###
First follow the steps to configure the container for macvlan (see above), and then add the following lines to your compose file:
After configuring the container for macvlan (see above), add the following lines to your compose file to enable DHCP:
```
environment:
@ -175,4 +157,4 @@ docker run -it --rm -e "BOOT=http://www.example.com/image.iso" --device=/dev/kvm
- 'c 510:* rwm'
```
NOTE: The exact cgroup rule may be different than `510` depending on your system, but the correct rule number will be printed to the log output in case of error.
Please note that the exact `cgroup` rule number may vary depending on your system, but the log output will indicate the correct number in case of an error.