Integration tests: container cleanup in applier subpackage

The integration testing suite for the applier subpackage creates two
containers for each test image, since this is necessary for testing sharding
functionality. Upon test completion, both containers are stopped but were not
destroyed. However, since all other package/subpackage testing suites only use
a single container per image, leaving the second container around is often
unnecessary.

This commit changes the applier subpackage's testing suite to only keep the
first container (per image) around, while destroying the second container.

Author: evanelias

applier/applier_test.go

@@ -88,7 +88,12 @@ func (s *ApplierIntegrationSuite) Teardown(backend string) error {
 	for n := range s.d {
 		n := n
 		g.Go(func() error {
-			return s.d[n].Stop()
+			// Only keep the first container; destroy any additional, since the other
+			// subpackages only use 1 test container
+			if n == 0 {
+				return s.d[n].Stop()
+			}
+			return s.d[n].Destroy()
 		})
 	}
 	return g.Wait()