Namespace ProtoTest.Testcontainers

ApplicationContainer: An application under test running in its own container image: the host starts it as run infrastructure, and the mapped address it serves on is published as the application's BaseUrl, so the application's REST clients, browser sessions and the readiness probe all resolve that one container. Register it as the target's UseContainer(container) provider with UseConfigured() first, so a configured address serves the target instead.

DockerProbe: The one availability probe for containers: whether the Docker daemon answers. A container provider condition reads it, so a machine without a container runtime skips the provider instead of failing the build.

ProtoContainerProviderExtensions: Registers a container piece as a target provider.

ProtoContainerResource<TContainer>: Base for a container owned by the run. The host starts it before the run, the started connection string fills a configuration key so tests and an in-process application see the same value, and the run releases it after the reports are written. Technology packages supply the builder and the connection accessor; the base depends on no container library.

ContainerStartResult<TResource>: The outcome of starting a container without throwing: the started resource, or the reason it could not start. A machine without a container runtime should be able to fall back or skip rather than fail the run, so a fixture decides on the result before registering the container.