Docker image Pipeline takes only 4 mins to complete build but now after 1 hour also build is running and failed finally

Question

Docker image Pipeline takes only 4 mins to complete build but now after 1 hour also build is running and failed finally

Sanginatham Venkata Nagendra 0

Hi Team,

Docker image build take only 4 mins to complete build, But suddenly after 1 hour also it is running and failed due to timeout. Please help on this. Attached pipelines logs. Please help us to resolve this issue.

Pipeline url: https://dev.azure.com/CAD-MGA/MGA-Administration-Platform/_build/results?buildId=1073&view=logs&j=275f1d19-1bd8-5591-b06b-07d489ea915a

Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-05T10:23:37.2266667+00:00

Hi Sanginatham Venkata Nagendra

We are not authorized to use the pipeline URL and please share the pipeline logs.

Also please share the docker template files.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Accepted answer

1 additional answer

Your answer

Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-05T10:23:37.2266667+00:00

Hi Sanginatham Venkata Nagendra

We are not authorized to use the pipeline URL and please share the pipeline logs.

Also please share the docker template files.
Deleted

This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.

Answer 1

Hi Sanginatham Venkata Nagendra

Change your docker-compose.yml volume to use an environment variable with a default:

volumes:
  - ${LOCAL_WWWROOT:-/tmp/wwwroot}:/app/wwwroot

Locally (Windows): LOCAL_WWWROOT points to c:\mga_xsc_api_qa
In CI (Linux): defaults to /tmp/wwwroot if LOCAL_WWWROOT is not set

In your classic pipeline’s Docker Compose build task:

Go to the Variables tab

Add:

Name: LOCAL_WWWROOT

  Value: `/tmp/wwwroot`
  
     Scope: Pipeline (not secret)

This way, during the build on Linux agents, docker-compose uses /tmp/wwwroot instead of c:\mga_xsc_api_qa.

In your pipeline task settings, add these environment variables to the Docker-related tasks:

DOCKER_BUILDKIT - 1

COMPOSE_DOCKER_CLI_BUILD - 1

This ensures docker-compose build uses BuildKit, which is faster and more stable on Microsoft-hosted agents.

Add timeout to prevent hanging:

timeout 600 docker-compose build xc.xsc.api

And also monitor this github for more updates - https://github.com/actions/runner-images/issues/12688

Hope this helps!

Please Let me know if you have any queries.

Answer 2

Sanginatham Venkata Nagendra 0

Hi Durga Reshma Malthi,

Please look into this asap as this is an urgent.

Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-06T05:55:01.1033333+00:00
Hi Sanginatham Venkata Nagendra

I am checking with the team internally as I suspect this could be a backend issue.

This could be related to this - https://github.com/actions/runner-images/issues/12688

It is still active.

Meanwhile please follow the below steps:

Add a .dockerignore file to exclude unnecessary files:
node_modules .git bin/ obj/ *.log

Enable BuildKit for faster and more efficient builds.
build: context: . dockerfile: XC.XSC.API/Dockerfile args: DOCKER_BUILDKIT: 1
or you can set in your pipeline:
variables: DOCKER_BUILDKIT: 1

Add --progress=plain to your Docker build command to get detailed output.

Run the same docker-compose build locally to see if it reproduces the issue.

You're mounting a Windows host path (c:\mga_xsc_api_qa) inside the container. But you're running on Linux hosted agent (ubuntu-24.04). On Linux, this path is invalid, which can cause the container build or run to hang indefinitely.

If you are using DockerCompose@0 then migrate to DockerCompose@1 or ``DockerCompose@2

If none of the steps solve this issue, then for immediate workaround please switch to use self-hosted agent - https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/windows-agent?view=azure-devops&tabs=IP-V4

And also disable buildkit in the pipeline.

$env:DOCKER_BUILDKIT = "0"

Example:

- task: DockerCompose@1 displayName: Build Images inputs: dockerComposeFile: '**/docker-compose.yml' # Use DOCKER_BUILDKIT=0 to avoid issues with Docker BuildKit in a bad Ubuntu image update (6/8/2025) dockerComposeFileArgs: DOCKER_BUILDKIT=0 projectName: ${PROJECT_NAME} qualifyImageNames: false action: 'Build services' additionalImageTags: '$(Build.BuildNumber)' arguments: '--build-arg FEED_ACCESSTOKEN=$(VSS_NUGET_ACCESSTOKEN)'

Additional References:

https://github.com/actions/runner-images/issues/12685

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-07T05:54:02.6366667+00:00

Hi Sanginatham Venkata Nagendra

Could you please try now and update us.

Feel free to reach out if you have any further queries.
Sanginatham Venkata Nagendra 0 Reputation points

2025-08-07T06:21:22.5966667+00:00

Hi Durga Reshma Malthi,

Still we are facing same issue, Please let me know any changes in docker compose file.
Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-07T06:51:00.9033333+00:00

Hi Sanginatham Venkata Nagendra

You can try the above steps which I have mentioned earlier

But for immediate workaround please switch to use self-hosted agent - https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/windows-agent?view=azure-devops&tabs=IP-V4

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-08T10:17:32.3866667+00:00

Hi Sanginatham Venkata Nagendra

Also try to change from docker-compose to docker.

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Sanginatham Venkata Nagendra 0 Reputation points

2025-08-08T14:30:35.06+00:00

Hi Durga Reshma Malthi,

We have tried given solution for docker compose file but no luck, Please let me know when it will be resolve because we are using docker compose files for many projects.
Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-11T06:57:13.5666667+00:00

Hi Sanginatham Venkata Nagendra

Could you please check this thread - https://learn.microsoft.com/en-us/answers/questions/5512231/single-devops-pipeline-for-react-js-application-fa

For immediate workaround please switch to use self-hosted agent - https://learn.microsoft.com/en-us/azure/devops/pipelines/agents/windows-agent?view=azure-devops&tabs=IP-V4

And also monitor this github for more updates - https://github.com/actions/runner-images/issues/12688

Hope this helps!

Please Let me know if you have any queries.
Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-12T07:53:12.23+00:00

Hi Sanginatham Venkata Nagendra

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Sanginatham Venkata Nagendra 0 Reputation points

2025-08-12T07:58:04.0833333+00:00

Hi Durga Reshma Malthi,

Provided resolution is not working for us and we are not ready to go with self hosted agent as it is cost based, So please provide alternate resolution to work docker compose file while building image using pipelines.

Durga Reshma Malthi 9,840 Microsoft External Staff Moderator

Hi Sanginatham Venkata Nagendra

Could you please try below steps:

Remove/Replace Host Path Volume for Cross-Platform Builds:

Update your docker-compose.yml:

  # Instead of this (only works on Windows):
  - c:\mga_xsc_api_qa:/app/wwwroot
  # Option 1: Use relative path or project dir volume if needed
  #   NOTE: Only if /app/wwwroot is needed during build/runtime.
  - ./local-dir:/app/wwwroot
  # Option 2: Remove this volume entirely if not needed in CI builds
  # (This is safest for Linux-based CI builds)

or try using DockerCompose@1 Task:

Update your pipeline like this:

  - task: DockerCompose@1
    displayName: Build and Push containers
    inputs:
      containerregistry: '<your-container-registry-service-connection>'
      dockerComposeFile: '**/docker-compose.yml'
      action: 'Build services'
      buildServices: 'xc.xsc.api'
      projectName: 'xsc-api'

Microsoft-hosted agents support BuildKit, which drastically improves build performance and reliability.

Add this to your pipeline YAML:

variables:
  DOCKER_BUILDKIT: 1
  COMPOSE_DOCKER_CLI_BUILD: 1

and add .dockerignore to root:

.git
node_modules
bin/
obj/
*.log
*.md
tests/

Add timeout to prevent hanging:

timeout 600 docker-compose build xc.xsc.api

And also monitor this github for more updates - https://github.com/actions/runner-images/issues/12688

Hope this helps!

Please Let me know if you have any queries.

Sanginatham Venkata Nagendra 0 Reputation points

2025-08-12T12:15:20.9866667+00:00

Hi Durga Reshma Malthi,

We are using classic build pipelines only. Please provide solution according to this.
Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-13T04:22:54.9+00:00

Hi Sanginatham Venkata Nagendra

Just checking in to see if you had a chance to review the response provided to your question.

Feel free to reach out if you have any further queries.
Sanginatham Venkata Nagendra 0 Reputation points

2025-08-13T08:46:16.51+00:00

Hi Durga Reshma Malthi,Thanks for your solution, Changes done as per your suggestion, Now we are able to build docker images using docker compose file.
Durga Reshma Malthi 9,840 Reputation points Microsoft External Staff Moderator

2025-08-13T08:49:10.01+00:00

Hi Sanginatham Venkata Nagendra

Thanks for your update.

If you found the information helpful, please click "Upvote" on the post to let us know and consider accepting the answer as the token of appreciation. Thank You.

Share via

Docker image Pipeline takes only 4 mins to complete build but now after 1 hour also build is running and failed finally

1 additional answer

Your answer