Nicolas De loof
Nicolas De loof
Thanks for reporting this issue with a detailed reproduction example.
Compose specification says: > Can be set as a range using syntax start-end, then actual port SHOULD be assigned within this range based on available ports. While arguably poorly documented,...
This is indeed a buildkit limitation. cc @tonistiigi
This issue depends on https://github.com/docker/buildx/issues/447 applies both on Docker Compose V2 and V1 as long as Buildkit is enabled (which is set by default on Docker Desktop)
for the record, cfp.io uses https://fullcalendar.io/ which is full-featured for GPL projects
@thaJeztah can you please transfert this issue to https://github.com/moby/buildkit ?
This volume permission issue is comparable to https://github.com/kubernetes/kubernetes/issues/2630. EFS exposing NFS binding option to translate uid/gid offers a workaround, but this still don't reproduce the docker volume experience, which created...
Can you please check CloudFormation web UI when deploying with `compose up` to know which resource triggered this "ClusterNotFoundException: Cluster not found" error? I can't see any reason it fails...
Thanks for digging into this. Can you please confirm you checked CloudFormation deployment ran by `compose up` in the expected eu-west-1 region? I hardly can imagine how `aws cloudformation` differs...
Please can you also check in the CloudFormation "model" UI that the uploaded template has the expected cluster ARN set for (failing) service?