Give tests access to inner Docker container if truly necessary

[michalvavrik]

Summary

I need to execute some actions on container post start (see here quarkusio/quarkus#35336 (comment), btw it didn't in fact solve my problems :-( so far) and I'd like bare metals to have access to Docker container if really necessary. It is not great option for it's bare metal Docker specific, but this option is available for only very rare cases. The way I use it, I use io.quarkus.test.bootstrap.BaseService#onPostStart and do org.testcontainers.containers.ContainerState#execInContainer(java.lang.String...).

Please check the relevant options

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Dependency update
• Refactoring
• Breaking change (fix or feature that would cause existing functionality to change)
• This change requires a documentation update
• This change requires execution against OCP (use run tests phrase in comment)

Checklist:

• Example scenarios has been updated / added
• Methods and classes used in PR scenarios are meaningful
• Commits are well encapsulated and follow the best practices

[michalvavrik]

Failures not related.

[mjurc]

Looks ok at first glance, let's see how the CI turns out

[michalvavrik]

Seen these failures already here #876, hence unrelated.