On Wed, Mar 29, 2017 at 5:40 PM, Burr Sutter <[email protected]> wrote:
> Turns out VirtualBox can go crazy too :-) > > https://screencast.com/t/4LBmdRjmes1o > > Inside the VM (minishift ssh), this is what top reports > > https://screencast.com/t/Yev6WZiwMn > > using beta3 > > > and which filesystem would the docker daemon be using? I wonder if my "du" process eating all the CPU is related to diskspace inside the VM. df -h Filesystem Size Used Avail Use% Mounted on /dev/mapper/live-rw 9.8G 797M 8.9G 9% / devtmpfs 2.9G 0 2.9G 0% /dev tmpfs 2.9G 0 2.9G 0% /dev/shm tmpfs 2.9G 26M 2.9G 1% /run tmpfs 2.9G 0 2.9G 0% /sys/fs/cgroup /dev/sr0 341M 341M 0 100% /run/initramfs/live /dev/sda1 18G 7.7G 9.3G 46% /mnt/sda1 tmpfs 583M 0 583M 0% /run/user/1000 > > On Wed, Mar 29, 2017 at 4:24 PM, Hardy Ferentschik <[email protected]> > wrote: > >> Hi, >> >> > Docker for Mac was using xhyve. I notice their docs now talk about >> HyperKit >> > https://docs.docker.com/docker-for-mac/install/#what- >> > to-know-before-you-install >> >> Yeah, HyperKit is the latest. We need to keep an eye on this. AFAIU from >> Dockers >> side HyperKit is the future. So I guess they are not so interested in >> libmachine >> anymore. >> >> > I wonder if thats better/different to xhyve? >> >> Not quite sure what HyperKit uses under the hood. One would think it >> builds on >> somehow on xhyve. I cannot imagine that they build a complete hypervisor. >> >> > Certainly we need to try keep up with Docker for UX. >> >> +1 >> >> --Hardy >> >> >
_______________________________________________ Devtools mailing list [email protected] https://www.redhat.com/mailman/listinfo/devtools
