The Amazon ECS CLI enables users to run their applications on ECS/Fargate using the Docker Compose file format, quickly provision resources, push/pull images in ECR, and monitor running applications on ECS/Fargate.
Specified the var/run/docker.sock file clearly instead of the var/run folder for the host mount configurations.
This file is created as a symbolic link with /Users/${username}/.docker/run/docker.sock in Mac environment.
With the folder mount configurations, /var/run/docker.sock is also created in a container as a symbolic link with the same path. Users or programs can not access the host's file path from inside a container, they cannot also access the socket file.
On the other hand, with the file mount configurations, /var/run/docker.sock is created as a genuine file, not a symbolic link. So they can access the socket file.
Specified the
var/run/docker.sockfile clearly instead of thevar/runfolder for the host mount configurations./Users/${username}/.docker/run/docker.sockin Mac environment./var/run/docker.sockis also created in a container as a symbolic link with the same path. Users or programs can not access the host's file path from inside a container, they cannot also access the socket file./var/run/docker.sockis created as a genuine file, not a symbolic link. So they can access the socket file.Fixed https://github.com/aws/amazon-ecs-cli/issues/1144
Enter
[N/A]in the box, if an item is not applicable to your change.Testing
Documentation
[N/A] Updated our README
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.