I also tried settinginstaller.paralleltofalsebut that didn't get me anywhere. I was tempted to disable themodern-installerbut that seemed too drastic of a step and I no longer felt like shooting in the dark. It would be great if the experts here could give me some pointers to try. I ...
If VMCache function is enabled, # kata-runtime will request VM from factory grpccache when it creates # a new sandbox. # # Default 0 #vm_cache_number = 0 # Specify the address of the Unix socket that is used by VMCache. # # Default /var/run/kata-containers/cache.sock #vm_cache...
yes checking does function 'ktime_get_real_seconds' exist... no checking does function 'ktime_get_real_ns' exist... yes checking does function 'ktime_to_timespec64' exist... yes checking does function 'timespec64_sub' exist... yes checking does function 'timespec64_to_ktime' exist.....
-- today at 3:30 PM Starting container with revision: b68db41955e7b444795fa38ec4d268318f63d0c7 today at 3:30 PM One or more OVERRIDE_DNS addresses found. Will use them to overwrite /etc/resolv.conf today at 3:30 PM Creating TUN device /dev/net/tun today at 3:30 PM mknod: /...
real 20m7.451s user 0m0.285s sys 0m0.280s I logged spun up a container for debugging: sudo docker run -it --privileged --volumes-from=pigen_work pi-gen /bin/bash Running thelosetupcommand manually for the root_dev worked: Ok, it's not so consistent. It made it past this failure ...
So, 'pip show modulename' doesn't work for os or other 'internal' python modules; seems to be only for other modules you've installed. Oh course, this is all empirical; what I've tried on the system I have (FWTW). 'pip show' didn't give me anything. So, I imported os then ...