[
https://issues.apache.org/jira/browse/FLINK-40653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martijn Visser updated FLINK-40653:
-----------------------------------
Fix Version/s: 2.4.0
> Testcontainers tests fail with "Could not find a valid Docker environment" on
> the cron_azure profile
> ----------------------------------------------------------------------------------------------------
>
> Key: FLINK-40653
> URL: https://issues.apache.org/jira/browse/FLINK-40653
> Project: Flink
> Issue Type: Bug
> Components: Build System
> Reporter: Martijn Visser
> Assignee: Martijn Visser
> Priority: Critical
> Labels: pull-request-available
> Fix For: 2.4.0
>
>
> Since the 2026-09-04 nightly every testcontainers based test in the
> {{test_cron_azure}} legs fails:
> {code}
> java.lang.IllegalStateException: Could not find a valid Docker environment.
> Please see logs and check configuration
> at
> org.testcontainers.dockerclient.DockerClientProviderStrategy.getFirstValidStrategy(DockerClientProviderStrategy.java:265)
> at
> org.apache.flink.core.testutils.TestContainerExtension.instantiateTestContainer(TestContainerExtension.java:59)
> {code}
> On master that is SeaweedFsTestContainerTest and
> SeaweedFsNativeS3TestContainerTest, on the release branches
> MinioTestContainerTest.
> The socket is not present at all. The {{Restore docker images}} task in the
> same job says:
> {code}
> failed to connect to the docker API at unix:///var/run/docker.sock; check if
> the path is correct and if the daemon is running: dial unix
> /var/run/docker.sock: connect: no such file or directory
> {code}
> Docker itself works on those agents. All four {{e2e_*_cron_azure}} jobs
> passed in the same build and they use Docker heavily. e2e-template.yml
> declares no container so they run on the host, while the test jobs run inside
> flink-build-container.
> {{cron_azure}} is the only stage in build-apache-repo.yml whose
> test_pool_definition is {{vmImage: 'ubuntu-24.04'}} instead of {{name:
> Default}}. The other five stages run the same tests in the same container on
> the ASF pool and pass.
> Last green nightly 78606 (2026-09-03), first red 78686 (2026-09-04), and all
> eleven master nightlies since fail the same way. FLINK-40548 is not the
> cause, it was committed after 78686 had already run.
> https://dev.azure.com/apache-flink/apache-flink/_build/results?buildId=79017
> template.flink-ci.yml works around this on GitHub Actions by chmod'ing the
> socket and setting DOCKER_HOST, but that only helps where the socket exists.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
