My application watches a large number of files, however, after setting a few thousand watches, the process inside the container begins to receive errors regarding the inotify limits. When I run the command to increase the watch limit in docker build (sudo sysctl fs.inotify.max_user_watches=<some random high number>), it gives an error from docker regarding "read-only filesystem" -- which is a [w

The issues described at minishift/minishift#2380 and kubernetes/minikube#1942 appear to now re-occur with the latest version when installing from Homebrew, although installing 0.3.3 manually works fine.

If a debug exception should fire after the execution of an instruction, we should inject the debug exception, which we are not currently doing.

https://howtohypervise.blogspot.com/2019/01/a-common-missight-in-most-hypervisors.html

Hi,
I have test runv for few weeks， make it a runtime work with docker, and it works well. but I still got problem when testing it, and I wanna to look for help from docs, unfortunately, I just find one doc in runv project. I think docs can add some docs like architecture about runv, guide about how to use .
maybe I not found them in network, but if you maintainer can put docs together in th

(...)

Having said that, I can see how _acquire_ implies a transition of some kind, so perhaps it'd be better to just change the docs (solo5.h) to say that you're only allowed to call it once per handle?

Originally posted by @mato in Solo5/solo5#402

I should show folks how to get up and running with VM sockets, so they don't need to do a bunch of Googling like I did.