MartijnVisser opened a new pull request, #29180:
URL: https://github.com/apache/flink/pull/29180
## What is the purpose of the change
Backport of FLINK-40653 to this branch. Azure Pipelines agent 5.279.0
stopped mapping `/var/run/docker.sock` into job containers on Linux, so every
testcontainers based test in a container job fails with "Could not find a valid
Docker environment". The `test_cron_azure` legs on this branch fail this way in
the nightly.
The other Azure stages still pass only because the ASF self-hosted agents
are on 5.278.0. They break the same way once those are upgraded. Fork pipelines
use `azure-pipelines.yml` on hosted agents and are affected already.
## Brief change log
* Set `mapDockerSocket: true` on the container resource in both pipeline
definitions
## Verifying this change
This change is a trivial rework / code cleanup without any test coverage.
It cannot be verified through a PR build. `azure-pipelines.yml` only
contains the `ci` and `ci_release` stages, so no PR run exercises `cron_azure`.
It needs a nightly or a manual run.
## Does this pull request potentially affect one of the following parts:
- Dependencies (does it add or upgrade a dependency): no
- The public API, i.e., is any changed class annotated with
`@Public(Evolving)`: no
- The serializers: no
- The runtime per-record code paths (performance sensitive): no
- Anything that affects deployment or recovery: JobManager (and its
components), Checkpointing, Kubernetes/Yarn, ZooKeeper: no
- The S3 file system connector: no
## Documentation
- Does this pull request introduce a new feature? no
- If yes, how is the feature documented? not applicable
---
##### Was generative AI tooling used to co-author this PR?
- [X] Yes (please specify the tool below)
Generated-by: Claude Code (Claude Opus 5)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
