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
{{ message }}
This repository has been archived by the owner on Nov 27, 2023. It is now read-only.
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:
Create a docker compose based off, e.g. a Minecraft image. Ensure the /server folder is mounted so that changes to configuration can be persisted.
Deploy the compose to ECS.
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:
Docker Compose version v2.7.0
Output of docker version:
Engine:
Version: 20.10.17
API version: 1.41 (minimum version 1.12)
Go version: go1.17.11
Git commit: a89b842
Built: Mon Jun 6 23:01:23 2022
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.6.6
GitCommit: 10c12954828e7c7c9b6e0ea9b0c02b01407d3ae1
runc:
Version: 1.1.2
GitCommit: v1.1.2-0-ga916309
docker-init:
Version: 0.19.0
GitCommit: de40ad0
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.
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
The text was updated successfully, but these errors were encountered: