# Dev Services Overview

Quarkus supports the automatic provisioning of unconfigured services in development and test mode. We refer to this capability as Dev Services. From a developer’s perspective this means that if you include an extension and don’t configure it then Quarkus will automatically start the relevant service (usually using Testcontainers behind the scenes) and wire up your application to use this service.

All this functionality is part of the Quarkus `deployment` modules, so does not affect the production application in any way. If you want to disable all Dev Services you can use the `quarkus.devservices.enabled=false` config property, although in most cases this is not necessary as simply configuring the service will result in the Dev Service being disabled automatically.

Note that the default startup timeout is 60s, if this is not enough you can increase it with the `quarkus.devservices.timeout` property.

This page lists all the Dev Services that Quarkus supports.

| In order to use Dev Services you will generally need a working Docker environment (remote environments are supported). If you don’t have Docker installed you will need to configure your services normally.

## AMQP

The AMQP Dev Service will be enabled when the `quarkus-smallrye-reactive-messaging-amqp` extension is present in your application, and the broker address has not been explicitly configured. More information can be found in the AMQP Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.amqp.devservices.enabled` If Dev Services for AMQP has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For AMQP, Dev Services starts a broker unless `amqp-host` or `amqp-port` are set or if all the Reactive Messaging AMQP channel are configured with `host` or `port`. Environment variable: `QUARKUS_AMQP_DEVSERVICES_ENABLED` | boolean |
`quarkus.amqp.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_AMQP_DEVSERVICES_PORT` | int |
`quarkus.amqp.devservices.image-name` The image to use. Note that only ActiveMQ Artemis images are supported. Specifically, the image repository must end with `artemiscloud/activemq-artemis-broker`. Check the activemq-artemis-broker on Quay page to find the available versions. Environment variable: `QUARKUS_AMQP_DEVSERVICES_IMAGE_NAME` | string | `quay.io/artemiscloud/activemq-artemis-broker:1.0.18`
`quarkus.amqp.devservices.extra-args` The value of the `AMQ_EXTRA_ARGS` environment variable to pass to the container. Environment variable: `QUARKUS_AMQP_DEVSERVICES_EXTRA_ARGS` | string | `--no-autotune --mapped --no-fsync --relax-jolokia --http-host 0.0.0.0`
`quarkus.amqp.devservices.shared` Indicates if the AMQP broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for AMQP starts a new container. The discovery uses the `quarkus-dev-service-amqp` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_AMQP_DEVSERVICES_SHARED` | boolean | `true`
`quarkus.amqp.devservices.service-name` The value of the `quarkus-dev-service-aqmp` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for AMQP looks for a container with the `quarkus-dev-service-amqp` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-amqp` label set to the specified value. This property is used when you need multiple shared AMQP brokers. Environment variable: `QUARKUS_AMQP_DEVSERVICES_SERVICE_NAME` | string | `amqp`
`quarkus.amqp.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_AMQP_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |

## Apicurio Registry

The Apicurio Dev Service will be enabled when the `quarkus-apicurio-registry-avro` extension is present in your application, and it’s address has not been explicitly configured. More information can be found in the Apicurio Registry Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.apicurio-registry.devservices.enabled` If Dev Services for Apicurio Registry has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For Apicurio Registry, Dev Services starts a registry unless `mp.messaging.connector.smallrye-kafka.apicurio.registry.url` or `mp.messaging.connector.smallrye-kafka.schema.registry.url` is set. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_ENABLED` | boolean |
`quarkus.apicurio-registry.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_PORT` | int |
`quarkus.apicurio-registry.devservices.image-name` The Apicurio Registry image to use. Note that only Apicurio Registry 2.x images are supported. Specifically, the image repository must end with `apicurio/apicurio-registry-mem`. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_IMAGE_NAME` | string | `quay.io/apicurio/apicurio-registry-mem:2.4.2.Final`
`quarkus.apicurio-registry.devservices.shared` Indicates if the Apicurio Registry instance managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Apicurio Registry starts a new container. The discovery uses the `quarkus-dev-service-apicurio-registry` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_SHARED` | boolean | `true`
`quarkus.apicurio-registry.devservices.service-name` The value of the `quarkus-dev-service-apicurio-registry` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Apicurio Registry looks for a container with the `quarkus-dev-service-apicurio-registry` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-apicurio-registry` label set to the specified value. This property is used when you need multiple shared Apicurio Registry instances. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_SERVICE_NAME` | string | `apicurio-registry`
`quarkus.apicurio-registry.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_APICURIO_REGISTRY_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |

## Databases

The database Dev Services will be enabled when a reactive or JDBC datasource extension is present in the application, and the database URL has not been configured. More information can be found in the Databases Dev Services Guide.

Quarkus provides Dev Services for all databases it supports. Most of these are run in a container, except H2 and Derby which are run in-process. Dev Services are supported for both JDBC and reactive drivers.

Those relational databases that are running in a container are started using Testcontainers and support "reusable instances"; this implies that if you add the property `testcontainers.reuse.enable=true` in your Testcontainers configuration file, a property file named `.testcontainers.properties` in your user home, then the databases will not be stopped aggressively after each run, and can be reused.

N.B. if you opt in for this feature, Quarkus will not reset the state of the database between runs unless you explicitly configure it to.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.datasource.devservices.enabled` `quarkus.datasource."datasource-name".devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_ENABLED` | boolean |
`quarkus.datasource.devservices.image-name` `quarkus.datasource."datasource-name".devservices.image-name` The container image name to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_IMAGE_NAME` | string |
`quarkus.datasource.devservices.container-env` `quarkus.datasource."datasource-name".devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |
`quarkus.datasource.devservices.container-properties` `quarkus.datasource."datasource-name".devservices.container-properties` Generic properties that are passed for additional container configuration. Properties defined here are database specific and are interpreted specifically in each database dev service implementation. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_CONTAINER_PROPERTIES` | `Map<String,String>` |
`quarkus.datasource.devservices.properties` `quarkus.datasource."datasource-name".devservices.properties` Generic properties that are added to the database connection URL. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_PROPERTIES` | `Map<String,String>` |
`quarkus.datasource.devservices.port` `quarkus.datasource."datasource-name".devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_PORT` | int |
`quarkus.datasource.devservices.command` `quarkus.datasource."datasource-name".devservices.command` The container start command to use, for container based DevServices providers. If the provider is not container based (e.g. a H2 Database) then this has no effect. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_COMMAND` | string |
`quarkus.datasource.devservices.db-name` `quarkus.datasource."datasource-name".devservices.db-name` The name of the database to use if this Dev Service supports overriding it. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_DB_NAME` | string |
`quarkus.datasource.devservices.username` `quarkus.datasource."datasource-name".devservices.username` The username to use if this Dev Service supports overriding it. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_USERNAME` | string |
`quarkus.datasource.devservices.password` `quarkus.datasource."datasource-name".devservices.password` The password to use if this Dev Service supports overriding it. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_PASSWORD` | string |
`quarkus.datasource.devservices.init-script-path` `quarkus.datasource."datasource-name".devservices.init-script-path` Path to a SQL script that will be loaded from the classpath and applied to the Dev Service database If the provider is not container based (e.g. an H2 or Derby Database) then this has no effect. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_INIT_SCRIPT_PATH` | string |
`quarkus.datasource.devservices.volumes` `quarkus.datasource."datasource-name".devservices.volumes` The volumes to be mapped to the container. The map key corresponds to the host location and the map value is the container location. If the host location starts with "classpath:", then the mapping will load the resource from the classpath with read-only permission. When using a file system location, the volume will be created with read-write permission, so the data in your file system might be wiped out or altered. If the provider is not container based (e.g. an H2 or Derby Database) then this has no effect. Environment variable: `QUARKUS_DATASOURCE_DEVSERVICES_VOLUMES` | `Map<String,String>` |

## Kafka

The Kafka Dev Service will be enabled when the `quarkus-kafka-client` extension is present in your application, and the broker address has not been explicitly configured. More information can be found in the Kafka Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.kafka.devservices.enabled` If Dev Services for Kafka has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For Kafka, Dev Services starts a broker unless `kafka.bootstrap.servers` is set or if all the Reactive Messaging Kafka channel are configured with a `bootstrap.servers`. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_ENABLED` | boolean |
`quarkus.kafka.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_PORT` | int |
`quarkus.kafka.devservices.provider` Kafka dev service container type. Redpanda, Strimzi and kafka-native container providers are supported. Default is redpanda. For Redpanda: See https://vectorized.io/docs/quick-start-docker/ and https://hub.docker.com/r/vectorized/redpanda For Strimzi: See https://github.com/strimzi/test-container and https://quay.io/repository/strimzi-test-container/test-container For Kafka Native: See https://github.com/ozangunalp/kafka-native and https://quay.io/repository/ogunalp/kafka-native Note that Strimzi and Kafka Native images are launched in Kraft mode. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_PROVIDER` | `redpanda`, `strimzi`, `kafka-native` | `redpanda`
`quarkus.kafka.devservices.image-name` The Kafka container image to use. Dependent on the provider. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_IMAGE_NAME` | string |
`quarkus.kafka.devservices.shared` Indicates if the Kafka broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Kafka starts a new container. The discovery uses the `quarkus-dev-service-kafka` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_SHARED` | boolean | `true`
`quarkus.kafka.devservices.service-name` The value of the `quarkus-dev-service-kafka` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Kafka looks for a container with the `quarkus-dev-service-kafka` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-kafka` label set to the specified value. This property is used when you need multiple shared Kafka brokers. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_SERVICE_NAME` | string | `kafka`
`quarkus.kafka.devservices.topic-partitions-timeout` Timeout for admin client calls used in topic creation. Defaults to 2 seconds. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_TOPIC_PARTITIONS_TIMEOUT` | Duration | `2S`
`quarkus.kafka.devservices.redpanda.transaction-enabled` Enables transaction support. Also enables the producer idempotence. Find more info about Red Panda transaction support on https://vectorized.io/blog/fast-transactions/. Notice that KIP-447 (producer scalability for exactly once semantic) and KIP-360 (Improve reliability of idempotent/transactional producer) are not supported. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_REDPANDA_TRANSACTION_ENABLED` | boolean | `true`
`quarkus.kafka.devservices.topic-partitions` The topic-partition pairs to create in the Dev Services Kafka broker. After the broker is started, given topics with partitions are created, skipping already existing topics. For example, `quarkus.kafka.devservices.topic-partitions.test=2` will create a topic named `test` with 2 partitions. The topic creation will not try to re-partition existing topics with different number of partitions. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_TOPIC_PARTITIONS` | `Map<String,Integer>` |
`quarkus.kafka.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_KAFKA_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |

| About the Duration format The format for durations uses the standard `java.time.Duration` format. You can learn more about it in the Duration#parse() javadoc. You can also provide duration values starting with a number. In this case, if the value consists only of a number, the converter treats the value as seconds. Otherwise, `PT` is implicitly prepended to the value to obtain a standard `java.time.Duration` format.

## Keycloak

The Keycloak Dev Service will be enabled when the `quarkus-oidc` extension is present in your application, and the server address has not been explicitly configured. More information can be found in the OIDC Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.keycloak.devservices.enabled` If DevServices has been explicitly enabled or disabled. When DevServices is enabled Quarkus will attempt to automatically configure and start Keycloak when running in Dev or Test mode and when Docker is running. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_ENABLED` | boolean | `true`
`quarkus.keycloak.devservices.image-name` The container image name to use, for container based DevServices providers. Image with a Quarkus based distribution is used by default. Image with a WildFly based distribution can be selected instead, for example: 'quay.io/keycloak/keycloak:19.0.3-legacy'. Note Keycloak Quarkus and Keycloak WildFly images are initialized differently. By default, Dev Services for Keycloak will assume it is a Keycloak Quarkus image if the image version does not end with a '-legacy' string. Set 'quarkus.keycloak.devservices.keycloak-x-image' to override this check. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_IMAGE_NAME` | string | `quay.io/keycloak/keycloak:22.0.1`
`quarkus.keycloak.devservices.keycloak-x-image` If Keycloak-X image is used. By default, Dev Services for Keycloak will assume a Keycloak-X image is used if the image name contains a 'keycloak-x' string. Set 'quarkus.keycloak.devservices.keycloak-x-image' to override this check which may be necessary if you build custom Keycloak-X or Keycloak images. You do not need to set this property if the default check works. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_KEYCLOAK_X_IMAGE` | boolean |
`quarkus.keycloak.devservices.shared` Indicates if the Keycloak container managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Keycloak starts a new container. The discovery uses the `quarkus-dev-service-label` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_SHARED` | boolean | `true`
`quarkus.keycloak.devservices.service-name` The value of the `quarkus-dev-service-keycloak` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Keycloak looks for a container with the `quarkus-dev-service-keycloak` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-keycloak` label set to the specified value. Container sharing is only used in dev mode. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_SERVICE_NAME` | string | `quarkus`
`quarkus.keycloak.devservices.realm-path` The comma-separated list of class or file system paths to Keycloak realm files which will be used to initialize Keycloak. The first value in this list will be used to initialize default tenant connection properties. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_REALM_PATH` | list of string |
`quarkus.keycloak.devservices.java-opts` The JAVA_OPTS passed to the keycloak JVM Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_JAVA_OPTS` | string |
`quarkus.keycloak.devservices.show-logs` Show Keycloak log messages with a "Keycloak:" prefix. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_SHOW_LOGS` | boolean | `false`
`quarkus.keycloak.devservices.start-command` Keycloak start command. Use this property to experiment with Keycloak start options, see `https://www.keycloak.org/server/all-config`. Note it will be ignored when loading legacy Keycloak WildFly images. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_START_COMMAND` | string |
`quarkus.keycloak.devservices.realm-name` The Keycloak realm name. This property will be used to create the realm if the realm file pointed to by the 'realm-path' property does not exist, default value is 'quarkus' in this case. If the realm file pointed to by the 'realm-path' property exists then it is still recommended to set this property for Dev Services for Keycloak to avoid parsing the realm file in order to determine the realm name. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_REALM_NAME` | string |
`quarkus.keycloak.devservices.create-realm` Indicates if the Keycloak realm has to be created when the realm file pointed to by the 'realm-path' property does not exist. Disable it if you’d like to create a realm using Keycloak Administration Console or Keycloak Admin API from `io.quarkus.test.common.QuarkusTestResourceLifecycleManager`. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_CREATE_REALM` | boolean | `true`
`quarkus.keycloak.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_PORT` | int |
`quarkus.keycloak.devservices.users` The Keycloak users map containing the username and password pairs. If this map is empty then two users, 'alice' and 'bob' with the passwords matching their names will be created. This property will be used to create the Keycloak users if the realm file pointed to by the 'realm-path' property does not exist. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_USERS` | `Map<String,String>` |
`quarkus.keycloak.devservices.roles` The Keycloak user roles. If this map is empty then a user named 'alice' will get 'admin' and 'user' roles and all other users will get a 'user' role. This property will be used to create the Keycloak roles if the realm file pointed to by the 'realm-path' property does not exist. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_ROLES` | `Map<String,List<String>>` |
`quarkus.keycloak.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_KEYCLOAK_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |

## Kubernetes

The Kubernetes Dev Service will be enabled when `kubernetes-client` extension is present in your application, and the API server address has not been explicitly configured. More information can be found in the Kubernetes Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Dev Services | Type | Default
--- | --- | ---
`quarkus.kubernetes-client.devservices.enabled` If Dev Services for Kubernetes should be used. (default to true) If this is true and kubernetes client is not configured then a kubernetes cluster will be started and will be used. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_ENABLED` | boolean | `true`
`quarkus.kubernetes-client.devservices.api-version` The kubernetes api server version to use. If not set, Dev Services for Kubernetes will use the latest supported version of the given flavor. see https://github.com/dajudge/kindcontainer/blob/master/k8s-versions.json Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_API_VERSION` | string |
`quarkus.kubernetes-client.devservices.flavor` The flavor to use (kind, k3s or api-only). Default to api-only. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_FLAVOR` | `kind`, `k3s`, `api-only` | `api-only`
`quarkus.kubernetes-client.devservices.override-kubeconfig` By default, if a kubeconfig is found, Dev Services for Kubernetes will not start. Set this to true to override the kubeconfig config. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_OVERRIDE_KUBECONFIG` | boolean | `false`
`quarkus.kubernetes-client.devservices.shared` Indicates if the Kubernetes cluster managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Kubernetes starts a new container. The discovery uses the `quarkus-dev-service-kubernetes` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_SHARED` | boolean | `true`
`quarkus.kubernetes-client.devservices.service-name` The value of the `quarkus-dev-service-kubernetes` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Kubernetes looks for a container with the `quarkus-dev-service-kubernetes` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-kubernetes` label set to the specified value. This property is used when you need multiple shared Kubernetes clusters. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_SERVICE_NAME` | string | `kubernetes`
`quarkus.kubernetes-client.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_KUBERNETES_CLIENT_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |

## MongoDB

The MongoDB Dev Service will be enabled when the `quarkus-mongodb-client` extension is present in your application, and the server address has not been explicitly configured. More information can be found in the MongoDB Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.mongodb.devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode. Environment variable: `QUARKUS_MONGODB_DEVSERVICES_ENABLED` | boolean |
`quarkus.mongodb.devservices.image-name` The container image name to use, for container based DevServices providers. Environment variable: `QUARKUS_MONGODB_DEVSERVICES_IMAGE_NAME` | string |
`quarkus.mongodb.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_MONGODB_DEVSERVICES_PORT` | int |
`quarkus.mongodb.devservices.properties` Generic properties that are added to the connection URL. Environment variable: `QUARKUS_MONGODB_DEVSERVICES_PROPERTIES` | `Map<String,String>` |
`quarkus.mongodb.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_MONGODB_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |

## RabbitMQ

The RabbitMQ Dev Service will be enabled when the `quarkus-smallrye-reactive-messaging-rabbitmq` extension is present in your application, and the broker address has not been explicitly configured. More information can be found in the RabbitMQ Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.rabbitmq.devservices.enabled` If Dev Services for RabbitMQ has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For RabbitMQ, Dev Services starts a broker unless `rabbitmq-host` or `rabbitmq-port` are set or if all the Reactive Messaging RabbitMQ channel are configured with `host` or `port`. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_ENABLED` | boolean |
`quarkus.rabbitmq.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_PORT` | int |
`quarkus.rabbitmq.devservices.http-port` Optional fixed port for the RabbitMQ management plugin. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_HTTP_PORT` | int |
`quarkus.rabbitmq.devservices.image-name` The image to use. Note that only official RabbitMQ images are supported. Specifically, the image repository must end with `rabbitmq`. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_IMAGE_NAME` | string | `rabbitmq:3.12-management`
`quarkus.rabbitmq.devservices.shared` Indicates if the RabbitMQ broker managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for RabbitMQ starts a new container. The discovery uses the `quarkus-dev-service-rabbitmq` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_SHARED` | boolean | `true`
`quarkus.rabbitmq.devservices.service-name` The value of the `quarkus-dev-service-rabbitmq` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for RabbitMQ looks for a container with the `quarkus-dev-service-rabbitmq` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-rabbitmq` label set to the specified value. This property is used when you need multiple shared RabbitMQ brokers. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_SERVICE_NAME` | string | `rabbitmq`
`quarkus.rabbitmq.devservices.exchanges."exchanges".type` Type of exchange: direct, topic, headers, fanout, etc. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__TYPE` | string | `direct`
`quarkus.rabbitmq.devservices.exchanges."exchanges".auto-delete` Should the exchange be deleted when all queues are finished using it? Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__AUTO_DELETE` | boolean | `false`
`quarkus.rabbitmq.devservices.exchanges."exchanges".durable` Should the exchange remain after restarts? Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__DURABLE` | boolean | `false`
`quarkus.rabbitmq.devservices.exchanges."exchanges".arguments` Extra arguments for the exchange definition. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_EXCHANGES__EXCHANGES__ARGUMENTS` | `Map<String,String>` |
`quarkus.rabbitmq.devservices.queues."queues".auto-delete` Should the queue be deleted when all consumers are finished using it? Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_QUEUES__QUEUES__AUTO_DELETE` | boolean | `false`
`quarkus.rabbitmq.devservices.queues."queues".durable` Should the queue remain after restarts? Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_QUEUES__QUEUES__DURABLE` | boolean | `false`
`quarkus.rabbitmq.devservices.queues."queues".arguments` Extra arguments for the queue definition. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_QUEUES__QUEUES__ARGUMENTS` | `Map<String,String>` |
`quarkus.rabbitmq.devservices.bindings."bindings".source` Source exchange to bind to. Defaults to name of binding instance. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__SOURCE` | string |
`quarkus.rabbitmq.devservices.bindings."bindings".routing-key` Routing key specification for the source exchange. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__ROUTING_KEY` | string | `#`
`quarkus.rabbitmq.devservices.bindings."bindings".destination` Destination exchange or queue to bind to. Defaults to name of binding instance. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__DESTINATION` | string |
`quarkus.rabbitmq.devservices.bindings."bindings".destination-type` Destination type for binding: queue, exchange, etc. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__DESTINATION_TYPE` | string | `queue`
`quarkus.rabbitmq.devservices.bindings."bindings".arguments` Extra arguments for the binding definition. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_BINDINGS__BINDINGS__ARGUMENTS` | `Map<String,String>` |
`quarkus.rabbitmq.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_RABBITMQ_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |

## Redis

The Redis Dev Service will be enabled when the `quarkus-redis-client` extension is present in your application, and the server address has not been explicitly configured. More information can be found in the Redis Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.redis.devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode and when Docker is running. Environment variable: `QUARKUS_REDIS_DEVSERVICES_ENABLED` | boolean | `true`
`quarkus.redis.devservices.image-name` The container image name to use, for container based DevServices providers. If you want to use Redis Stack modules (bloom, graph, search…​), use: `redis/redis-stack-server:latest`. Environment variable: `QUARKUS_REDIS_DEVSERVICES_IMAGE_NAME` | string |
`quarkus.redis.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_REDIS_DEVSERVICES_PORT` | int |
`quarkus.redis.devservices.shared` Indicates if the Redis server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Redis starts a new container. The discovery uses the `quarkus-dev-service-redis` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_REDIS_DEVSERVICES_SHARED` | boolean | `true`
`quarkus.redis.devservices.service-name` The value of the `quarkus-dev-service-redis` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Redis looks for a container with the `quarkus-dev-service-redis` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-redis` label set to the specified value. This property is used when you need multiple shared Redis servers. Environment variable: `QUARKUS_REDIS_DEVSERVICES_SERVICE_NAME` | string | `redis`
`quarkus.redis.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_REDIS_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |
`quarkus.redis."additional-redis-clients".devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode and when Docker is running. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_ENABLED` | boolean | `true`
`quarkus.redis."additional-redis-clients".devservices.image-name` The container image name to use, for container based DevServices providers. If you want to use Redis Stack modules (bloom, graph, search…​), use: `redis/redis-stack-server:latest`. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_IMAGE_NAME` | string |
`quarkus.redis."additional-redis-clients".devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_PORT` | int |
`quarkus.redis."additional-redis-clients".devservices.shared` Indicates if the Redis server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Redis starts a new container. The discovery uses the `quarkus-dev-service-redis` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_SHARED` | boolean | `true`
`quarkus.redis."additional-redis-clients".devservices.service-name` The value of the `quarkus-dev-service-redis` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Redis looks for a container with the `quarkus-dev-service-redis` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-redis` label set to the specified value. This property is used when you need multiple shared Redis servers. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_SERVICE_NAME` | string | `redis`
`quarkus.redis."additional-redis-clients".devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_REDIS__ADDITIONAL_REDIS_CLIENTS__DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |

## Vault

The Vault Dev Service will be enabled when the `quarkus-vault` extension is present in your application, and the server address has not been explicitly configured. More information can be found in the Vault Guide.

## Neo4j

The Neo4j Dev Service will be enabled when the `quarkus-neo4j` extension is present in your application, and the server address has not been explicitly configured. More information can be found in the Neo4j Guide.

## Infinispan

The Infinispan Dev Service will be enabled when the `quarkus-infinispan-client` extension is present in your application, and the server address has not been explicitly configured. More information can be found in the Infinispan Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.infinispan-client.devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode and when Docker is running. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_ENABLED` | boolean | `true`
`quarkus.infinispan-client.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_PORT` | int |
`quarkus.infinispan-client.devservices.shared` Indicates if the Infinispan server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Infinispan starts a new container. The discovery uses the `quarkus-dev-service-infinispan` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_SHARED` | boolean | `true`
`quarkus.infinispan-client.devservices.service-name` The value of the `quarkus-dev-service-infinispan` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Infinispan looks for a container with the `quarkus-dev-service-infinispan` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-infinispan` label set to the specified value. This property is used when you need multiple shared Infinispan servers. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_SERVICE_NAME` | string | `infinispan`
`quarkus.infinispan-client.devservices.image-name` The image to use. Note that only official Infinispan images are supported. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_IMAGE_NAME` | string |
`quarkus.infinispan-client.devservices.artifacts` List of the artifacts to automatically download and add to the Infinispan server libraries. For example a Maven coordinate (org.postgresql:postgresql:42.3.1) or a dependency location url. If an invalid value is passed, the Infinispan server will throw an error when trying to start. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_ARTIFACTS` | list of string |
`quarkus.infinispan-client.devservices.site` Add a site name to start the Infinispan Server Container with Cross Site Replication enabled (ex. lon). Cross Site Replication is the capability to connect two separate Infinispan Server Clusters that might run in different Data Centers, and configure backup caches to copy the data across the clusters with active-active or active-passive replication. See more about Cross Site Replication in the Infinispan Documentation https://infinispan.org/docs/stable/titles/xsite/xsite.html Configure `mcast-port` to avoid forming a cluster with any other running Infinispan Server container. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_SITE` | string |
`quarkus.infinispan-client.devservices.mcast-port` If you are running an Infinispan Server already in docker, if the containers use the same mcastPort they will form a cluster. Set a different mcastPort to create a separate cluster in Docker (e. 46656). A common use case in a local Docker development mode, is the need of having two different Infinispan Clusters with Cross Site Replication enabled. see https://github.com/infinispan/infinispan-simple-tutorials/blob/main/infinispan-remote/cross-site-replication/docker-compose/ Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_MCAST_PORT` | int |
`quarkus.infinispan-client.devservices.tracing.enabled` Runs the Infinispan Server container with tracing enabled. Traces are disabled by default Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_TRACING_ENABLED` | boolean | `false`
`quarkus.infinispan-client.devservices.tracing.exporter.otlp.endpoint` Sets Infinispan Server otlp endpoint. Default value is http://localhost:4317 Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_TRACING_EXPORTER_OTLP_ENDPOINT` | string | `http://localhost:4317`
`quarkus.infinispan-client.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_INFINISPAN_CLIENT_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |
`quarkus.infinispan-client."named-infinispan-clients".devservices.enabled` If DevServices has been explicitly enabled or disabled. DevServices is generally enabled by default, unless there is an existing configuration present. When DevServices is enabled Quarkus will attempt to automatically configure and start a database when running in Dev or Test mode and when Docker is running. Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_ENABLED` | boolean | `true`
`quarkus.infinispan-client."named-infinispan-clients".devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_PORT` | int |
`quarkus.infinispan-client."named-infinispan-clients".devservices.shared` Indicates if the Infinispan server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Infinispan starts a new container. The discovery uses the `quarkus-dev-service-infinispan` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_SHARED` | boolean | `true`
`quarkus.infinispan-client."named-infinispan-clients".devservices.service-name` The value of the `quarkus-dev-service-infinispan` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Infinispan looks for a container with the `quarkus-dev-service-infinispan` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise, it starts a new container with the `quarkus-dev-service-infinispan` label set to the specified value. This property is used when you need multiple shared Infinispan servers. Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_SERVICE_NAME` | string | `infinispan`
`quarkus.infinispan-client."named-infinispan-clients".devservices.image-name` The image to use. Note that only official Infinispan images are supported. Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_IMAGE_NAME` | string |
`quarkus.infinispan-client."named-infinispan-clients".devservices.artifacts` List of the artifacts to automatically download and add to the Infinispan server libraries. For example a Maven coordinate (org.postgresql:postgresql:42.3.1) or a dependency location url. If an invalid value is passed, the Infinispan server will throw an error when trying to start. Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_ARTIFACTS` | list of string |
`quarkus.infinispan-client."named-infinispan-clients".devservices.site` Add a site name to start the Infinispan Server Container with Cross Site Replication enabled (ex. lon). Cross Site Replication is the capability to connect two separate Infinispan Server Clusters that might run in different Data Centers, and configure backup caches to copy the data across the clusters with active-active or active-passive replication. See more about Cross Site Replication in the Infinispan Documentation https://infinispan.org/docs/stable/titles/xsite/xsite.html Configure `mcast-port` to avoid forming a cluster with any other running Infinispan Server container. Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_SITE` | string |
`quarkus.infinispan-client."named-infinispan-clients".devservices.mcast-port` If you are running an Infinispan Server already in docker, if the containers use the same mcastPort they will form a cluster. Set a different mcastPort to create a separate cluster in Docker (e. 46656). A common use case in a local Docker development mode, is the need of having two different Infinispan Clusters with Cross Site Replication enabled. see https://github.com/infinispan/infinispan-simple-tutorials/blob/main/infinispan-remote/cross-site-replication/docker-compose/ Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_MCAST_PORT` | int |
`quarkus.infinispan-client."named-infinispan-clients".devservices.tracing.enabled` Runs the Infinispan Server container with tracing enabled. Traces are disabled by default Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_TRACING_ENABLED` | boolean | `false`
`quarkus.infinispan-client."named-infinispan-clients".devservices.tracing.exporter.otlp.endpoint` Sets Infinispan Server otlp endpoint. Default value is http://localhost:4317 Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_TRACING_EXPORTER_OTLP_ENDPOINT` | string | `http://localhost:4317`
`quarkus.infinispan-client."named-infinispan-clients".devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_INFINISPAN_CLIENT__NAMED_INFINISPAN_CLIENTS__DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |

## Elasticsearch

The Elasticsearch Dev Service will be enabled when one of the Elasticsearch based extensions (Elasticsearch client or Hibernate Search ORM Elasticsearch) is present in your application, and the server address has not been explicitly configured. More information can be found in the Elasticsearch Dev Services Guide.

Configuration property fixed at build time - All other configuration properties are overridable at runtime

Configuration property | Type | Default
--- | --- | ---
`quarkus.elasticsearch.devservices.enabled` If Dev Services for Elasticsearch has been explicitly enabled or disabled. Dev Services are generally enabled by default, unless there is an existing configuration present. For Elasticsearch, Dev Services starts a server unless `quarkus.elasticsearch.hosts` is set. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_ENABLED` | boolean |
`quarkus.elasticsearch.devservices.port` Optional fixed port the dev service will listen to. If not defined, the port will be chosen randomly. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_PORT` | int |
`quarkus.elasticsearch.devservices.image-name` The Elasticsearch container image to use. Defaults to the elasticsearch image provided by Elastic. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_IMAGE_NAME` | string | `docker.elastic.co/elasticsearch/elasticsearch:8.8.2`
`quarkus.elasticsearch.devservices.java-opts` The value for the ES_JAVA_OPTS env variable. Defaults to setting the heap to 512MB min - 1GB max. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_JAVA_OPTS` | string | `-Xms512m -Xmx1g`
`quarkus.elasticsearch.devservices.shared` Indicates if the Elasticsearch server managed by Quarkus Dev Services is shared. When shared, Quarkus looks for running containers using label-based service discovery. If a matching container is found, it is used, and so a second one is not started. Otherwise, Dev Services for Elasticsearch starts a new container. The discovery uses the `quarkus-dev-service-elasticsearch` label. The value is configured using the `service-name` property. Container sharing is only used in dev mode. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_SHARED` | boolean | `true`
`quarkus.elasticsearch.devservices.service-name` The value of the `quarkus-dev-service-elasticsearch` label attached to the started container. This property is used when `shared` is set to `true`. In this case, before starting a container, Dev Services for Elasticsearch looks for a container with the `quarkus-dev-service-elasticsearch` label set to the configured value. If found, it will use this container instead of starting a new one. Otherwise it starts a new container with the `quarkus-dev-service-elasticsearch` label set to the specified value. This property is used when you need multiple shared Elasticsearch servers. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_SERVICE_NAME` | string | `elasticsearch`
`quarkus.elasticsearch.devservices.container-env` Environment variables that are passed to the container. Environment variable: `QUARKUS_ELASTICSEARCH_DEVSERVICES_CONTAINER_ENV` | `Map<String,String>` |