Update readme.md

This commit is contained in:
Kroese 2023-03-26 20:44:23 +02:00 committed by GitHub
parent b0b44657c0
commit f4d7df24b5
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23

View File

@ -1,10 +1,10 @@
# virtual-dsm
[![Test](https://github.com/joshkunz/qemu-docker/actions/workflows/test.yaml/badge.svg)](https://github.com/joshkunz/qemu-docker/actions/workflows/test.yaml)
[![Test](https://github.com/kroese/virtual-dsm/actions/workflows/test.yaml/badge.svg)](https://github.com/kroese/virtual-dsm/actions/workflows/test.yaml)
This repository contains a Docker container for running Synology's Virtual DSM.
A docker container for running Synology's Virtual DSM.
Docker Hub: [jkz0/qemu](https://hub.docker.com/r/jkz0/qemu)
Docker Hub: [kroese/virtual-dsm](https://hub.docker.com/r/kroese/virtual-dsm/)
## Using the container
@ -40,18 +40,7 @@ services:
restart: always
```
## Tips
## How to use
* 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.
* a
* b