Update using_docker_images.md

This commit is contained in:
Paul 2017-10-22 15:51:09 +00:00 committed by Paul B
parent 090aefdc24
commit 5f0663cacf
1 changed files with 0 additions and 4 deletions

View File

@ -327,10 +327,6 @@ means, that when starting the container without additional options, it will run
the database's process, while Runner expects that the image will have no the database's process, while Runner expects that the image will have no
entrypoint or at least will start with a shell as its entrypoint. entrypoint or at least will start with a shell as its entrypoint.
Previously we would need to create our own image based on the
`super/sql:experimental` image, set the entrypoint to a shell, and then use
it in job's configuration, e.g.:
Before the new extended Docker configuration options, you would need to create Before the new extended Docker configuration options, you would need to create
your own image based on the `super/sql:experimental` image, set the entrypoint your own image based on the `super/sql:experimental` image, set the entrypoint
to a shell and then use it in job's configuration, like: to a shell and then use it in job's configuration, like: