Change Details

... specifically for the use case of Fresh, but possibly also more generally which might inform how we'd run testing short-mid term for Blubber, Beaker test for operations/puppet, and anything that either needs to run Docker itself or needs its own VM for other reasons. Some things to think about: * [x] Docker-in-Docker (D-in-D): Probably not feasible. Basically requires giving the executable access to the host. Either by granting the first container root (so that the second one can be spawned inside), or by granting the first container access to the host docker socket so that it can spawn the second one as a sibling, directly on the host. * [ ] Let the Jenkins job create a VM (using Qemu/KVM), and then run git-clone and test command inside that. (The VM would resume from a snapshot with docker, git, etc. pre-installed).

... specifically for the use case of Fresh, but possibly also more generally which might inform how we'd run testing short-mid term for Blubber, Beaker test for operations/puppet, and anything that either needs to run Docker itself or needs its own VM for other reasons. Some things to think about: * [x] Docker-in-Docker (D-in-D): Probably not feasible. Basically requires giving the executable access to the host. Either by granting the first container root (so that the second one can be spawned inside), or by granting the first container access to the host docker socket so that it can spawn the second one as a sibling, directly on the host. * [x] Let the Jenkins job create a VM (using Qemu/KVM), and then run git-clone and test command inside that. (The VM would resume from a snapshot with docker, git, etc. pre-installed).

... specifically for the use case of Fresh, but possibly also more generally which might inform how we'd run testing short-mid term for Blubber, Beaker test for operations/puppet, and anything that either needs to run Docker itself or needs its own VM for other reasons. Some things to think about: * [x] Docker-in-Docker (D-in-D): Probably not feasible. Basically requires giving the executable access to the host. Either by granting the first container root (so that the second one can be spawned inside), or by granting the first container access to the host docker socket so that it can spawn the second one as a sibling, directly on the host. * [ * [x] Let the Jenkins job create a VM (using Qemu/KVM), and then run git-clone and test command inside that. (The VM would resume from a snapshot with docker, git, etc. pre-installed).