> For the complete documentation index, see [llms.txt](https://docs.portainer.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.portainer.io/user/docker/services/configure.md).

# Configure service options

From the menu select **Services** then select the service you want to configure.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/QlYdsDJBvoLxYcsi7Apu/Select-service-new.gif" alt=""><figcaption></figcaption></figure>

## Service details

In this section you can:

* View a summary of the details about the service.
* Configure the number of replicas.
* Toggle the [service webhook](/user/docker/services/webhooks.md) on or off.
* View the [service logs](/user/docker/services/logs.md).
* Update, [roll back](/user/docker/services/rollback.md) or delete the service.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/JSEYtksvcq6vTsEMJxtB/2.15-docker_services_service_details.png" alt=""><figcaption></figcaption></figure>

## Container specification configuration options

### Change container image

Here you can replace the container image with a different image. Select the registry, enter the image name, then click **Apply changes**.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/GidrmrEtSiZqcAW9Ppof/2.15-docker_services_change_container_image.png" alt=""><figcaption></figcaption></figure>

### Environment variables

It's best to set environment variables when you [create a container](/user/docker/containers/add.md) and before deployment. You can still set or edit these variables after deployment if you wish.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/GIDqfTrsaLWWsftqz4Wt/2.15-docker_services_service_env_var.png" alt=""><figcaption></figcaption></figure>

### Container labels

Labels give you a way to record information about a container, such as the way it's configured. Labels can also be used by Portainer to [hide containers from the interface](/admin/settings.md#hidden-containers).

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/Re9rBDYlHqcb6QSEUnAg/2.15-docker_services_service_container_labels.png" alt=""><figcaption></figcaption></figure>

### Mounts

You have the option to either mount or bind volumes in Portainer, and you can also make them read only. To add a mount, first select either **Volume** or **Bind** from the **Type** dropdown.

#### For volume mounts:

Select the volume from the **Source** dropdown, enter the container path in the **Target** field tick **Read only** if required then click **Apply changes**.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/srjoBKIh77x70mnAG05I/2.15-docker_services_service_mounts_volume.png" alt=""><figcaption></figcaption></figure>

#### For bind mounts:

Enter the source path in the **Source** field, enter the container path in the **Target** field, tick **Read only** if required then click **Apply changes**.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/R200xUIdzsss4w8qoSTw/2.15-docker_services_service_mounts_bind.png" alt=""><figcaption></figcaption></figure>

## Networks & ports configuration options

### Networks

You can define one or more networks for a service either before or after deployment. Simply select the network from the dropdown then click **Apply changes**.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/DYxKPJD4vxKYRJZE8EHE/2.15-docker_services_service_networks.png" alt=""><figcaption></figcaption></figure>

### Published ports

Use this setting to publish ports so they can access a container from outside of the host. You can either add new ports or update existing ports.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/1bk8CmoF4eFIuejjAtH0/2.15-docker_services_service_published_ports.png" alt=""><figcaption></figcaption></figure>

### Hosts file entries

Lets you manually specify a hostname or URL and associate the URL to an internal or external IP address.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/KCudRtoqGeOSrixKJVqO/2.15-docker_services_service_host_entries.png" alt=""><figcaption></figcaption></figure>

## Service specification settings

### Resource limits and reservations

Sets limits on resource utilization, such as memory, CPU reservation and CPU limit.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/hzwxHpFQVSzHc0ylAHhb/2.15-docker_services_service_resource_limits.png" alt=""><figcaption></figcaption></figure>

### Placement constraints

Use placement constraints to control which nodes a service can be assigned to.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/1g7yvJvcbSOpPr3GDqli/2.15-docker_services_service_placement_constraint.png" alt=""><figcaption></figcaption></figure>

### Placement preferences

While placement constraints limit the nodes a service can run on, placement preferences attempt to place tasks on appropriate nodes in an algorithmic way (by default they are spread evenly).

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/eLNIoAwXPdCdWZNhCVaB/2.15-docker_services_service_placement_pref.png" alt=""><figcaption></figcaption></figure>

### Restart policy

Docker's restart policies ensure that linked containers are restarted in the correct order, and control the conditions under which they are restarted:

* **Any**: Restart the container under any conditions (restarted host or Docker daemon).
* **On Failure**: Restart the container if it exits due to an error which manifests as a non-zero exit code.
* **None**: Do not automatically restart the container.

You can also adjust the restart delay, maximum attempts and restart window.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/lxTOk04lk1qJXLkkJUKN/2.15-docker_services_service_restart_policy.png" alt=""><figcaption></figcaption></figure>

### Update configuration

Updates a service according to the parameters you specify. The parameters specified here are the same as `docker service create` (see [Docker's own documentation](https://docs.docker.com/engine/reference/commandline/service_create/) for more information).

Normally, updating a service will only cause the service’s tasks to be replaced with new ones if a change to the service requires recreating the tasks for it to take effect.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/XTorHFbIOwMSQkQhyyu1/2.15-docker_services_service_update_config.png" alt=""><figcaption></figcaption></figure>

### Logging driver

Docker includes logging mechanisms called *logging drivers* that get information from the containers and services you're running. Each Docker daemon has a default logging driver which each container will use, unless you configure them to use a different logging driver.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/uemp3X7HeSRre7VqLqTX/2.15-docker_services_service_logging_driver.png" alt=""><figcaption></figcaption></figure>

### Service labels

Lets you add metadata to containers using Docker labels either via an array or a dictionary. We recommend that you use reverse-DNS notation to stop labels from conflicting with those used by other software.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/vVKHelp0kSzne1UgugtY/2.15-docker_services_service_labels.png" alt=""><figcaption></figcaption></figure>

### Configs

Docker 17.06 introduced Swarm service configs. These allow you to store non-sensitive information such as configuration files outside a service’s image or running containers. This keeps images as generic as possible and removes the need to bind-mount configuration files into containers or use environment variables.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/lRKPhgWg9ey52qSu84fC/2.15-docker_services_service_configs.png" alt=""><figcaption></figcaption></figure>

### Secrets

In the context of Docker Swarm services, a secret is a blob of data such as a password, SSH private key, SSL certificate, or another piece of data that should not be transmitted over a network or stored unencrypted in a Dockerfile or in your application’s source code.

<figure><img src="https://content.gitbook.com/content/MmwXfSb4bP3JyB8BLrAf/blobs/b8STPohM6W4Rhi1xmyoN/2.15-docker_services_service_secrets.png" alt=""><figcaption></figcaption></figure>