Skip to content

fix: update docker-compose.yml for Compose v5 compatibility - #2177

Closed
Battleplus wants to merge 1 commit into
unclecode:mainfrom
Battleplus:fix/2091-compose-v5-compat
Closed

fix: update docker-compose.yml for Compose v5 compatibility#2177
Battleplus wants to merge 1 commit into
unclecode:mainfrom
Battleplus:fix/2091-compose-v5-compat

Conversation

@Battleplus

Copy link
Copy Markdown

What

  • Remove obsolete version: '3.8' attribute
  • Move pids_limit from top level to deploy.resources.limits.pids

Why

Fixes #2091 - docker-compose.yml is rejected by Compose v5 with 'can't set distinct values on pids_limit'.

Changes

  • Removed version: '3.8' (obsolete, causes warnings)
  • Moved pids_limit: 512 to deploy.resources.limits.pids: 512 (compose-spec-compliant)

Testing

  • Verified the compose file is valid with docker compose config

Fixes #2091

- Remove obsolete 'version: 3.8' attribute
- Move pids_limit from top level to deploy.resources.limits.pids
- This fixes the 'can't set distinct values on pids_limit' error in Compose v5

Fixes unclecode#2091

Signed-off-by: Battleplus <3559424769@qq.com>
@Battleplus

Copy link
Copy Markdown
Author

Closing as superseded by #2094, already merged into develop, which moves the PID cap to deploy.resources.limits.pids and removes the obsolete Compose version field as part of the complete issue fix.

@Battleplus Battleplus closed this Aug 22, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

[Bug]: Docker(0.9.x): Compose file invalid on Compose v5, silent API removals, misleading auth failure modes

1 participant