avast/gradle-docker-compose-plugin

Problem with container logs

Open

#436 opened on Feb 1, 2024

View on GitHub
 (0 comments) (4 reactions) (0 assignees)Groovy (429 stars) (103 forks)batch import
help wanted

Description

web: image: web healthcheck: interval: 5s timeout: 5s retries: 60 test: curl -sS http://127.0.0.1 || echo 1

worker image: worker depends_on: web: { condition: service_healthy }

if I use depends_on then container logs start writing (captureContainersOutputToFiles = 'build/compose_log') only when all containers accept the UP(it's starting) status that is, when 'web' starts - 'worker' has the 'create' status until the web takes on the healthy status and logs will be written to the 'build/compose_log' folder only after that, so in case of problems with raising the ' web' container, the logs will be in the folder is not written, this is very inconvenient, can I do something about it?

Contributor guide

Tech stack
dockergroovy
Domain
devopstesting
Issue type
bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
fresh
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Docker Composehealth checks
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40
Research direction
Investigate the plugin's source code to understand when container log output is captured. Look for references to 'captureContainersOutputToFiles' and 'healthcheck' in the main plugin classes. Consider modifying the log capture to start as soon as the container starts, rather than waiting for all containers to become healthy.