Julio Montes

> What actually happens when you do this on a host/guest that support it. Do you see a window? No, > The only way we could merge something like this...

Hi All I think the best way to avoid restoring proxy's state is a redesign in the way we connect cc-shims and the container, we can hot plug virtio serial...

I prefer to do not include bash or any other utility that will not be used by the agent, less components -> less CVEs -> less vulnerabilities

we can create a debugeable image running next command: ``` make clean $ EXTRA_PKGS="dbus-bin dbus-autostart util-linux-bin p11-kit-bin bash shadow ca-certs dist-pam-configs xz-bin tar-bin grep-bin sed-bin pigz-bin iproute2-bin procps-ng-bin psstop-bin htop-bin...

@jcvenegas how many MB increase the image size?

I wouldn't like to include bash in the "production" version of the CC image because I want to avoid any possible container escape (i.e chroot /proc/1/cwd)