![]() You can choose to remove all images used by any service or only images that don't have a custom tag set in the image field. This is similar to using the -compatibility option with the docker-compose command.Ĭonfigure which images should be removed when stopping and removing containers. This is similar to using the -v or -volumes option with the docker-compose down command.Ĭonvert v3 service definitions into v2 compatible parameters. ![]() ![]() When stopping and removing containers, also delete named volumes declared in the Docker Compose file and anonymous volumes attached to containers. This is similar to setting the DOCKER_BUILDKIT=1 environment variable when invoking the docker build command. Use the BuildKit backend when building the images. env in the directory with the Docker Compose file. This is similar to using the -env-file option with the docker-compose command.īy default, the Docker Compose run configuration looks for a file named. Specify the path to a custom environment file that defines the Docker Compose environment variables. They are not passed on to any of the containers. These are used only by the Docker Compose process. Specify the Docker Compose environment variables. This is similar to using the -p option with the docker-compose command. By default, it is the name of the current directory. ![]() Specify an alternate project name for Docker Compose. Use the Modify options menu to add advanced options to the run configuration: If this option is disabled, you can open the tool window manually: Show the run configuration settings before actually starting it.ĭepending on the type of configuration, open the Run, Debug, or Services tool window when you start this run configuration. Click to remove the selected task from the list. Select a task and click to edit the task. Move tasks in the list using and to change the order in which to perform the tasks. For example, run another configuration, build the necessary artifacts, run some external tool or a web browser, and so on.Ĭlick or press Alt+Insert to add one of the available tasks. Specify a list of tasks to perform before starting the run configuration. Specify the services to build, create, and start.Ĭlick to select services that are listed in the YML file. This is similar to using the -f option with the docker-compose command. Docker Compose builds the configuration in the specified order, so any subsequent files override and add to the fields of the same service in previous files. Specify the compose files that define the necessary services. Select the Docker daemon connection to use for the run configuration. idea directory, you can save the configuration to any other directory within the project.īy default, it is disabled, and PhpStorm stores run configuration settings in. However, if you do not want to share the. Save the file with the run configuration settings to share it with other team members. This is helpful when a run configuration consumes a lot of resources and there is no good reason to run multiple instances. Specify a name for the run configuration to quickly identify it among others when editing or running.Īllow running multiple instances of this run configuration in parallel.īy default, it is disabled, and when you start this configuration while another instance is still running, PhpStorm suggests stopping the running instance and starting another one.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |