This is an automated email from the ASF dual-hosted git repository.

aicam pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/texera.git


The following commit(s) were added to refs/heads/main by this push:
     new 05bb34810e fix: test failure from testcontainer caused by docker 
update raising minimum version (#4208)
05bb34810e is described below

commit 05bb34810e75bfd51f092e331dbefe61bd3d1bf8
Author: Matthew B. <[email protected]>
AuthorDate: Thu Feb 12 18:55:50 2026 -0800

    fix: test failure from testcontainer caused by docker update raising 
minimum version (#4208)
    
    <!--
    Thanks for sending a pull request (PR)! Here are some tips for you:
    1. If this is your first time, please read our contributor guidelines:
    [Contributing to
    Texera](https://github.com/apache/texera/blob/main/CONTRIBUTING.md)
      2. Ensure you have added or run the appropriate tests for your PR
      3. If the PR is work in progress, mark it a draft on GitHub.
      4. Please write your PR title to summarize what this PR proposes, we
        are following Conventional Commits style for PR titles as well.
      5. Be sure to keep the PR description updated to reflect all changes.
    -->
    
    ### What changes were proposed in this PR?
    <!--
    Please clarify what changes you are proposing. The purpose of this
    section
    is to outline the changes. Here are some tips for you:
      1. If you propose a new API, clarify the use case for a new API.
      2. If you fix a bug, you can clarify why it is a bug.
      3. If it is a refactoring, clarify what has been changed.
      3. It would be helpful to include a before-and-after comparison using
         screenshots or GIFs.
      4. Please consider writing useful notes for better and faster reviews.
    -->
    
    This PR updates the CI test environment configuration to ensure
    integration tests that rely on containerized services can reliably
    connect to the local container runtime after recent runner image
    updates. It does this by adding a small configuration file in the
    runtime environment (the docker client properties file) so the Docker
    client and server negotiate a compatible API version, preventing
    container-based test suites from aborting during setup.
    
    ### Any related issues, documentation, discussions?
    <!--
    Please use this section to link other resources if not mentioned
    already.
    1. If this PR fixes an issue, please include `Fixes #1234`, `Resolves
    #1234`
    or `Closes #1234`. If it is only related, simply mention the issue
    number.
      2. If there is design documentation, please add the link.
      3. If there is a discussion in the mailing list, please add the link.
    -->
    Related to recent CI runner image updates that changed Docker behavior
    and can cause container-based tests to abort when the Docker client API
    version is not explicitly configured.
    
    ### How was this PR tested?
    <!--
    If tests were added, say they were added here. Or simply mention that if
    the PR
    is tested with existing test cases. Make sure to include/update test
    cases that
    check the changes thoroughly including negative and positive cases if
    possible.
    If it was tested in a way different from regular unit tests, please
    clarify how
    you tested step by step, ideally copy and paste-able, so that other
    reviewers can
    test and check, and descendants can verify in the future. If tests were
    not added,
    please describe why they were not added and/or why it was difficult to
    add.
    -->
    Ran the existing test suite in CI to verify that container-based
    integration test suites no longer abort during setup.
    
    Confirmed that the workflow completes successfully with no aborted
    suites.
    
    ### Was this PR authored or co-authored using generative AI tooling?
    <!--
    If generative AI tooling has been used in the process of authoring this
    PR,
    please include the phrase: 'Generated-by: ' followed by the name of the
    tool
    and its version. If no, write 'No'.
    Please refer to the [ASF Generative Tooling
    Guidance](https://www.apache.org/legal/generative-tooling.html) for
    details.
    -->
    Reviewed by Gemini 3
---
 .github/workflows/github-action-build.yml | 4 ++++
 common/workflow-core/build.sbt            | 2 +-
 file-service/build.sbt                    | 2 +-
 3 files changed, 6 insertions(+), 2 deletions(-)

diff --git a/.github/workflows/github-action-build.yml 
b/.github/workflows/github-action-build.yml
index 646ce4a119..e7b277cc99 100644
--- a/.github/workflows/github-action-build.yml
+++ b/.github/workflows/github-action-build.yml
@@ -130,6 +130,10 @@ jobs:
           PGPASSWORD: postgres
       - name: Compile with sbt
         run: sbt clean package
+      - name: Set docker-java API version
+        run: |
+          echo "api.version=1.52" >> ~/.docker-java.properties
+          cat ~/.docker-java.properties
       - name: Run backend tests
         run: sbt test
 
diff --git a/common/workflow-core/build.sbt b/common/workflow-core/build.sbt
index 99870f03eb..db91668513 100644
--- a/common/workflow-core/build.sbt
+++ b/common/workflow-core/build.sbt
@@ -83,7 +83,7 @@ Test / PB.protoSources += PB.externalSourcePath.value
 // Test-related Dependencies
 /////////////////////////////////////////////////////////////////////////////
 
-val testcontainersVersion = "0.43.0"
+val testcontainersVersion = "0.44.1"
 
 libraryDependencies ++= Seq(
   "org.scalamock" %% "scalamock" % "5.2.0" % Test,                  // 
ScalaMock
diff --git a/file-service/build.sbt b/file-service/build.sbt
index 34b30472e0..0697a68871 100644
--- a/file-service/build.sbt
+++ b/file-service/build.sbt
@@ -54,7 +54,7 @@ Compile / scalacOptions ++= Seq(
 val dropwizardVersion = "4.0.7"
 val mockitoVersion = "5.4.0"
 val assertjVersion = "3.24.2"
-val testcontainersVersion = "0.43.0"
+val testcontainersVersion = "0.44.1"
 
 /////////////////////////////////////////////////////////////////////////////
 // Test-related Dependencies

Reply via email to