-
Notifications
You must be signed in to change notification settings - Fork 303
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Error attempting to ecs-cli compose up #11
Comments
Have the same problem with even such a simple configuration: data-container:
image: mongo:3.1.9
volumes:
- /data/db looks like volumes are not working at all? When this gonna be fixed, and is there a temporary solution for now? |
|
@previa, the build option is not supported at the moment, you will have to supply the image name. |
Any news on |
I do also face this problem. Is there any workaround? |
FYI, a workaround here: Just use |
👍 for this as well. It would be nice to be able to use |
Hi @uttarasridhar has there been any movement on this issue? |
FYI, another workaround if you don't have access to modify the Dockerfile: Specify the host path explicitly, even if it is the same as the source path. e.g.
|
Any ETA here? |
Just got this working using
|
Created a cluster running on two instances like specified in the examples.
This is my compose file (
docker-compose-prod.yml
):When I run:
Seems that
sourcePath
is not getting set as it should be in the task definition.The text was updated successfully, but these errors were encountered: