This way you can supply a `boot.iso`, `boot.img` or `boot.qcow2` file. The URL of the `BOOT` variable will be ignored in this case.
This way you can supply a `boot.iso`, `boot.img` or `boot.qcow2` file.
* ### How do I boot ARM images?
> [!NOTE]
> The URL of the `BOOT` variable will be ignored in this case.
### How do I boot ARM images?
You can use [qemu-arm](https://github.com/qemus/qemu-arm/) to run ARM64-based images.
*### How do I boot Windows?
### How do I boot Windows?
Use [dockur/windows](https://github.com/dockur/windows) instead, as it includes all the drivers required during installation, amongst many other features.
*### How do I boot macOS?
### How do I boot macOS?
Use [dockur/macos](https://github.com/dockur/macos) instead, as it uses all the right settings and automaticly downloads the installation files.
*### How do I boot without VirtIO drivers?
### How do I boot without VirtIO drivers?
By default, the machine makes use of `virtio-scsi` drives for performance reasons, and even though most Linux kernels bundle the necessary driver for this device, that may not always be the case for other operating systems.
If it still fails to boot, you can set the value to `ide` to emulate a IDE drive, which is slow but requires no drivers and is compatible with almost every system.
> [!TIP]
> If it still fails to boot, you can set the value to `ide` to emulate a IDE drive, which is slow but requires no drivers and is compatible with almost every system.
*### How do I change the amount of CPU or RAM?
### How do I change the amount of CPU or RAM?
By default, the container will be allowed to use a maximum of 1 CPU core and 1 GB of RAM.
If you didn't receive any error from `kvm-ok` at all, but the container still complains that `/dev/kvm` is missing, it might help to add `privileged: true` to your compose file (or `--privileged` to your `run` command), to rule out any permission issue.
*### How do I assign an individual IP address to the container?
### How do I assign an individual IP address to the container?
By default, the container uses bridge networking, which shares the IP address with the host.
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.
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, you need to create a [second macvlan](https://blog.oddbit.com/post/2018-03-12-using-docker-macvlan-networks/#host-access) as a workaround.
> [!IMPORTANT]
> 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, you need to create a [second macvlan](https://blog.oddbit.com/post/2018-03-12-using-docker-macvlan-networks/#host-access) as a workaround.
*### How can the VM acquire an IP address from my router?
### How can the VM acquire an IP address from my router?
After configuring the container for macvlan (see above), it is possible for the VM to become part of your home network by requesting an IP from your router, just like a real PC.
Please note that in this mode, the container and the VM will each have their own separate IPs. The container will keep the macvlan IP, and the VM will use the DHCP IP.
> [!NOTE]
> In this mode, the container and the VM will each have their own separate IPs.
*### How do I add multiple disks?
### How do I add multiple disks?
To create additional disks, modify your compose file like this: