Hi Antonio, the solution currently implemented does indeed test the installed package: it will install it using /etc/apt/sources.list.d/autopkgtest.list, and run the entire upstream test suite against that. You are right that all of this happens in a docker container.
This is because that all the dependencies and requirements for that test suite to run are a bit complex, and upstream's solution uses docker for setting all that up: our initial implementation therefore chose that as well. There is however an ongoing effort to rewrite it shell, so as to directly use the underlying host. Once that effort is complete, disk usage shouldn't be a problem anymore on the debci workers. Cheers, -- Seb
