[BUG] start_interval parameter for docker compose latest version v2.26.1 healthcheck

[fti-akumari]

Description

I am encountering an issue with the start_interval parameter inDocker Compose version 2.26.1.It seems that the start_interval functionality is not working as expected in this version, whereas it functions properly in version 2.24.5.

Problem:

When attempting to use the start_interval parameter in version 2.26.1, I consistently encounter errors. However, in version 2.24.5, the same configuration works without any issues.

Error Message:

Reference

Expected Behavior:

The start_interval parameter should work consistently across different versions of Docker Compose. When specifying a start interval for a service, Docker Compose should honor this configuration and start the service accordingly.

Steps To Reproduce

• Use Docker Compose version 2.26.1.
• Configure a service with the start_interval parameter set to a specific value.
• Attempt to deploy the service using Docker Compose.
• Observe the error or unexpected behavior related to the start_interval parameter.

Compose Version

Docker Compose version v2.26.1

Docker Environment

Anything else?

No response

[glours]

Hello @fti-akumari
Thanks for opening the issue
I can't reproduce on my side, I used the sample given in the stackoverflow issue and here the output I have when running Docker Compose v2.26.1 and Docker Engine 26.0.0

> bat compose.yaml
───────┬──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
       │ File: compose.yaml
───────┼──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
   1   │ services:
   2   │   postgres:    # this is just an example, please don't focus on that particular image
   3   │     image: postgres:15-alpine
   4   │     environment:
   5   │       POSTGRES_PASSWORD: toto
   6   │     healthcheck:
   7   │       test: pg_isready -d my_db -U my_user    # again, the command here is not my point, nor the env, feel free to change it
   8   │       interval: 60s
   9   │       start_period: 30s
  10   │       start_interval: 5s
───────┴──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────────
> docker compose version
Docker Compose version v2.26.1
> docker version
Client:
 Cloud integration: v1.0.35+desktop.13
 Version:           26.0.0
 API version:       1.45
 Go version:        go1.21.8
 Git commit:        2ae903e
 Built:             Wed Mar 20 15:14:46 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.30.0 (143875)
 Engine:
  Version:          26.0.0
  API version:      1.45 (minimum version 1.24)
  Go version:       go1.21.8
  Git commit:       8b79278
  Built:            Wed Mar 20 15:18:02 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0
> docker compose up
[+] Running 1/0
 ✔ Container issue-11683-postgres-1  Created                                                                                                                                                                                             0.0s
Attaching to postgres-1
postgres-1  |
postgres-1  | PostgreSQL Database directory appears to contain a database; Skipping initialization
postgres-1  |
postgres-1  | 2024-04-03 14:23:56.634 UTC [1] LOG:  starting PostgreSQL 15.6 on aarch64-unknown-linux-musl, compiled by gcc (Alpine 13.2.1_git20231014) 13.2.1 20231014, 64-bit
postgres-1  | 2024-04-03 14:23:56.634 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
postgres-1  | 2024-04-03 14:23:56.634 UTC [1] LOG:  listening on IPv6 address "::", port 5432
postgres-1  | 2024-04-03 14:23:56.636 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
postgres-1  | 2024-04-03 14:23:56.640 UTC [24] LOG:  database system was shut down at 2024-04-03 14:23:29 UTC
postgres-1  | 2024-04-03 14:23:56.644 UTC [1] LOG:  database system is ready to accept connections
postgres-1  | 2024-04-03 14:24:01.638 UTC [34] FATAL:  role "my_user" does not exist

Do you have an another sample or more details to reproduce your issue?

[fti-akumari]

Thanks for replying so quickly.
I have checked it again with fresh machine, it is working as expected now.
And sorry for my late reply.