Open chrisbecke opened 2 years ago
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
This issue has been automatically closed because it had not recent activity during the stale period.
Description
It is established docker behavior that when docker creates a volume, if the folder in the image already contains files the volume is pre-populated with those files. When deploying services to an ECS context, volume creation behavior is not honored.
Steps to reproduce the issue:
/server
folder is mounted so that changes to configuration can be persisted.Describe the results you received:
The image does not start as the entrypoint cannot find the minecraft_server.jar file. The minecraft_server.jar file starts out in the /server folder, but as this folder is mounted, it is not present.
Describe the results you expected:
One of (in descending order of preference) A. The contents of the folder to populate the created AWS::EFS::Filesystem object. B. Docker compose to warn that the generated Filesystem will be empty, but the image is not. C. The Documentation to call out this change from expected behaviour.
Output of
docker-compose --version
:Output of
docker version
:Additional environment details (AWS ECS, Azure ACI, local, etc.):
AWS ECS