Comments (11)
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.
data:
image: tianon/true
volumes:
- /opt/data:/opt/data
from amazon-ecs-cli.
👍 for this as well. It would be nice to be able to use volumes
in the compose file or at LEAST provide a better error that it fails because of volumes.
from amazon-ecs-cli.
Hi @uttarasridhar has there been any movement on this issue?
from amazon-ecs-cli.
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?
from amazon-ecs-cli.
FYI, a workaround here:
Just use VOLUME
at the end of your relevant Dockerfile
. This will do what you want. Then remove the non-host-specific volume
entry from your docker-compose.yml
file.
from amazon-ecs-cli.
Just got this working using
volumes: ["/hostshare:/containershare"]
from amazon-ecs-cli.
Any ETA here?
from amazon-ecs-cli.
mysql:
build: .
command: /usr/sbin/mysqld --basedir=/usr --datadir=/var/lib/mysql --plugin-dir=/usr/lib/mysql/plugin --user=mysql --log-error=/var/log/mysql/error.log --pid-file=/var/run/mysqld/mysqld.pid --socket=/var/run/mysqld/mysqld.sock --port=3306 --bind-address=0.0.0.0
# https://github.com/docker-library/mysql/blob/master/5.6/Dockerfile
ports:
- "3306:3306"
solr:
build: .
working_dir: /root/solr/example/
command: java -jar start.jar
ports:
- "8984:8984"
ui:
build: .
working_dir: /root/insurance_ui/
command: python httpd.py
ports:
- "9090:9090"
api:
build: .
working_dir: /root/insurance_api/
command: python manage.py runserver 0.0.0.0:7000
ports:
- "7000:7000"
links:
- mysql:mysql
- solr:solr
➜ ecs ./ecs-cli compose -f docker-compose.yml up
WARN[0000] Skipping unsupported YAML option... option name=build
WARN[0000] Skipping unsupported YAML option... option name=working_dir
WARN[0000] Skipping unsupported YAML option... option name=build
WARN[0000] Skipping unsupported YAML option... option name=working_dir
WARN[0000] Skipping unsupported YAML option... option name=build
WARN[0000] Skipping unsupported YAML option... option name=working_dir
WARN[0000] Skipping unsupported YAML option... option name=build
ERRO[0000] Error registering task definition error=ClientException: Container.image should not be null or empty.
status code: 400, request id: 61061f57-9361-11e5-b7e7-99c8fdd92fa9 family=0xc2080bf640
ERRO[0000] Create task definition failed error=ClientException: Container.image should not be null or empty.
status code: 400, request id: 61061f57-9361-11e5-b7e7-99c8fdd92fa9
FATA[0000] ClientException: Container.image should not be null or empty.
status code: 400, request id: 61061f57-9361-11e5-b7e7-99c8fdd92fa9
from amazon-ecs-cli.
@previa, the build option is not supported at the moment, you will have to supply the image name.
from amazon-ecs-cli.
Any news on ClientException: host.sourcePath should not be blank
I need a volume to share between my instances, but I don't want it to be persistent.
from amazon-ecs-cli.
I do also face this problem. Is there any workaround?
from amazon-ecs-cli.
Related Issues (20)
- Feat. Request: Allow environment variables to depend on CF intrinsic functions
- `ecs-cli local up` badly handles secrets if the docker-compose container name has dashes
- `ecs-cli local create` should docker-compose escape the env vars in entrypoint
- ECS_CONTAINER_METADATA_URI is not accessible in macOS
- ecs-cli compose task failing with "Fargate only supports network mode ‘awsvpc’"
- Question: can I override the location of config and credential files?
- Support OSX Arm64
- EKS - Creating nodegroup
- Allow specifying container parameters (cpu, memory) using ecs params HOT 1
- global --endpoint flag is not supported
- Launch Templates vs Launch Configurations HOT 3
- Link to "Information about specific compose versions and fields supported by the ecs-cli" is broken
- when I run a task locally it does not seem to pickup environment variable containing values from parameterstore
- Create ecs-service from ecs-cli
- Problem with Task not working when creating Docker Volume driver with capital letter "Local"
- [Feature Request] depends_on option in ecs params
- Add support for readonlyrootfilesystem schema
- How to copy files into ECS container?
- unable to pull image HOT 1
- User-data script has erroneous newline breaking shebang, incompatible with Cloud-init versions on AL2023 HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from amazon-ecs-cli.