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
The doc recommends using Docker for installation, but all the CLI examples assume that the runs are not done with a Docker installation.
we should separate non-Docker, debug and development-style CLI runs from the regular production CLI runs where the installation was done with Docker
in order to add local input files to a project using the CLI, extra arguments needs to be passed to docker-compose
For instance with --volume /absolute/source/path/on/host:/absolute/target/path/in/container:ro this mounts and makes available /absolute/source/path/on/host on host to the /absolute/target/path/in/container path inside the container (and :ro means read only)
For instance a full command to create a project with my local file at /home/foo/code/image.tar could be:
$ docker-compose run \
--volume /home/foo/code:/foo:ro web \
./manage.py create-project my-project \
--pipeline docker \
--input-file="/foo/image.tar"
The text was updated successfully, but these errors were encountered:
The doc recommends using Docker for installation, but all the CLI examples assume that the runs are not done with a Docker installation.
For instance with
--volume /absolute/source/path/on/host:/absolute/target/path/in/container:ro
this mounts and makes available/absolute/source/path/on/host
on host to the/absolute/target/path/in/container
path inside the container (and :ro means read only)For instance a full command to create a project with my local file at
/home/foo/code/image.tar
could be:$ docker-compose run \ --volume /home/foo/code:/foo:ro web \ ./manage.py create-project my-project \ --pipeline docker \ --input-file="/foo/image.tar"
The text was updated successfully, but these errors were encountered: