You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Drop docker-compose fork, use upstream with dockerd MTU propagation
The gitpod-io/compose fork's only change — reading MTU from ceth0 to
set it on compose-created networks — has been broken since Feb 2023
when the workspace interface was renamed from ceth0 to eth0 (40830a8).
The MTU override has been silently skipped for 3+ years.
Instead of maintaining the fork, propagate MTU to compose-created
networks via dockerd's --default-network-opt flag (supported since
Docker 27.0; we ship 27.5.1). docker-up already reads the correct
MTU from eth0 for --mtu and --network-control-plane-mtu.
Changes:
- docker-up: add --default-network-opt=bridge=com.docker.network.driver.mtu
- WORKSPACE.yaml: update dockerComposeVersion to upstream 2.40.3
- dependencies.sh: download from docker/compose instead of gitpod-io/compose
This eliminates the critical grpc CVE (GHSA-p77j-4mvh-x3m3) in the
forked docker-compose binary and restores the MTU behavior that was
silently broken.
Co-authored-by: Ona <no-reply@ona.com>
0 commit comments