New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] start_interval parameter for docker compose latest version v2.26.1 healthcheck #11683
Comments
Hello @fti-akumari > 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? |
Thanks for replying so quickly. |
Description
I am encountering an issue with the start_interval parameter in
Docker 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 version2.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
Compose Version
Docker Compose version v2.26.1
Docker Environment
Anything else?
No response
The text was updated successfully, but these errors were encountered: