From 5f0663cacf9d8d351b17862a372d0de33f0d57ca Mon Sep 17 00:00:00 2001 From: Paul Date: Sun, 22 Oct 2017 15:51:09 +0000 Subject: [PATCH] Update using_docker_images.md --- doc/ci/docker/using_docker_images.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/doc/ci/docker/using_docker_images.md b/doc/ci/docker/using_docker_images.md index fa823ea4721..f7493794b6a 100644 --- a/doc/ci/docker/using_docker_images.md +++ b/doc/ci/docker/using_docker_images.md @@ -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 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 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: