> For the complete documentation index, see [llms.txt](https://docs.cybus.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cybus.io/2-6-1/deployment/upgrading-connectware/on-docker/to-2-6-0-on-docker.md).

# Upgrading Connectware to 2.6.0 (Docker)

How to upgrade Connectware to version 2.6.0 on Docker.

Connectware 2.6.0 adds OpenMetrics endpoints for core components, new Rule Engine functions, and OPC UA namespace URI support. For a complete list of changes, see the [2.6.0 changelog](https://docs.cybus.io/2-6-1/deployment/upgrading-connectware/on-docker/pages/veQnb7pmTbxcaG8seqYD#connectware-2.6.0).

{% hint style="warning" %}

## Check your upgrade path

The steps in this guide apply to specific setups. Before you continue, check [Connectware Upgrade Paths](/2-6-1/deployment/upgrading-connectware/upgrade-paths.md) to determine which upgrades and steps apply to your installation.
{% endhint %}

Complete the following steps in order, as one upgrade operation.

{% stepper %}
{% step %}

## InfluxDB 3 Endpoints: Rename Measurement to Table

This step applies if you have services with `Influxdb3` endpoints that use the `measurement` or `measurementPrefix` properties, or that receive messages carrying a `measurement` key on the `/set` topic. Check your service commissioning files for endpoints with `protocol: Influxdb3`. If you do not use the `Influxdb3` protocol, skip this step.

Connectware 2.6.0 renames the `measurement` and `measurementPrefix` endpoint properties to `table` and `tablePrefix` to align with InfluxDB 3 terminology. The `Influxdb` (InfluxDB 2) protocol keeps `measurement` and `measurementPrefix`.

Update the affected service commissioning files, then upgrade. Connectware 2.5.0 does not accept `table` or `tablePrefix`, so do not install the updated files before the upgrade.

{% code lineNumbers="true" %}

```yaml
resources:
  machineMetricsWrite:
    type: Cybus::Endpoint
    properties:
      protocol: Influxdb3
      connection: !ref influxdb3Connection
      write:
        table: machine_metrics # was: measurement
        tags:
          line: assembly-1
```

{% endcode %}

Update any application that publishes a `measurement` key to the `/set` topic of an `Influxdb3` endpoint to send `table` instead.

For more information, see [InfluxDB 3 Support](/2-6-1/connectors/enterprise-connectors/influxdb.md#influxdb-3-support).
{% endstep %}

{% step %}

## Agents on Docker: Change the Network Mode to Bridge

This step applies if you deploy agents with Docker or Docker Compose. If all your agents run on Kubernetes, skip this step.

Agents running the protocol-mapper 2.6.0 image bind port `8888` for their health probe and port `9184` for their metrics endpoint. Agents that run with `network_mode: host` share the host's ports, so only the first one to start binds them. The remaining agents stop during bootstrap with an `EADDRINUSE` error.

Change the affected agents to bridge networking:

{% code lineNumbers="true" %}

```yaml
services:
  protocol-mapper-agent:
    network_mode: bridge
```

{% endcode %}

If you start agents with `docker run`, replace `--network=host` with `--network=bridge`.

With bridge networking, `localhost` refers to the container, not the host. Set `CYBUS_HOSTNAME_INGRESS` to an address that reaches Connectware from inside the container.

For more information, see [Network Mode](/2-6-1/data-flows/agents/installing-agents/installing-agents-via-docker-compose.md#network-mode).
{% endstep %}

{% step %}

## Upgrading Connectware to 2.6.0

Follow the instructions in [Upgrading Connectware (Docker)](/2-6-1/deployment/upgrading-connectware/on-docker.md) to upgrade to version 2.6.0.
{% endstep %}
{% endstepper %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.cybus.io/2-6-1/deployment/upgrading-connectware/on-docker/to-2-6-0-on-docker.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.