You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: README.md
+54Lines changed: 54 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -163,6 +163,7 @@ RunCVM features:
163
163
-[Advanced usage](#advanced-usage)
164
164
-[Developing](#developing)
165
165
-[Building](#building)
166
+
-[Testing](#testing)
166
167
-[Contributing](#contributing)
167
168
-[Support](#support)
168
169
-[Uninstallation](#uninstallation)
@@ -636,6 +637,59 @@ The build script creates a Docker image named `newsnowlabs/runcvm:latest`.
636
637
637
638
Now follow the main [installation instructions](#installation) to install your built RunCVM from the Docker image.
638
639
640
+
## Testing
641
+
642
+
Test RunCVM using nested RunCVM. You can do this using a Docker image capable of installing RunCVM, or an image built with a version of RunCVM preinstalled.
(Uncomment the final block to build an image with RunCVM preinstalled, or leave the block commented to test RunCVM installation).
677
+
678
+
To launch, run:
679
+
680
+
```sh
681
+
docker run -d --runtime=runcvm -m 2g --name=ubuntu-docker-runcvm ubuntu-docker-runcvm
682
+
```
683
+
684
+
> Optionally modify this `docker run` command by:
685
+
> - adding `--rm` - to automatically remove the container after systemd shutdown
686
+
> - removing `-d` and adding `--env=RUNCVM_KERNEL_DEBUG=1` - to see kernel and systemd boot logs
687
+
> - removing `-d` and adding `-it` - to provide a console
688
+
689
+
Then `docker exec -it -u runcvm ubuntu-docker-runcvm bash` to obtain a command prompt and perform testing.
690
+
691
+
Run `docker rm -fv ubuntu-docker-runcvm` to clean up after testing.
692
+
639
693
## Support
640
694
641
695
**Support launching images:** If you encounter any Docker image that launches in a standard container runtime that does not launch in RunCVM, or launches but with unexpected behaviour, please [raise an issue](https://github.com/newsnowlabs/runcvm/issues) titled _Launch failure for image `<image>`_ or _Unexpected behaviour for image `<image>`_ and include log excerpts and an explanation of the failure, or expected and unexpected behaviour.
0 commit comments