Migrating to v0.15.0

Scanopy v0.15.0 consolidates the previously separate discovery types (Network Scan, Docker, Self-Report) into a single discovery flow. Daemons now run one discovery that handles network scanning, Docker container discovery, and self-reporting together. Credentials are managed through a universal credential store instead of per-daemon configuration.

Most of the migration is automatic — but there are a few things you need to do manually.

What Happens Automatically

When a daemon running v0.15.0 or later connects, the server:

1. Deletes all legacy discoveries (Network Scan, Docker, Self-Report) associated with that daemon
2. Creates a single new discovery that combines the functionality of all three
3. Preserves your scan schedules and subnet configuration

What You Need to Do

1. Recreate Docker proxy configuration as a credential

If you configured Docker proxy via daemon config (--docker-proxy, SCANOPY_DOCKER_PROXY, or the config file), you need to recreate it as a Docker Proxy credential in the UI.

1. Go to Assets > Credentials
2. Click Create Credential
3. Select Docker Proxy as the type
4. Enter the proxy port (default: 2376), optional path, and SSL certificates if applicable
5. Save the credential
6. Assign it to the target host from the host edit modal (Credentials tab)

The daemon config flags (--docker-proxy, --docker-proxy-ssl-cert, --docker-proxy-ssl-key, --docker-proxy-ssl-chain) still work in v0.15.0 but log deprecation warnings. They will be removed in v0.16.0.

See the Docker Proxy guide for the full setup process.

2. Re-apply scan speed overrides

If you customized scan speed settings in daemon config (--scan-rate-pps, --arp-rate-pps, etc.), those daemon-level values are no longer used. Scan speed is now configured per-discovery.

1. Go to Discover > Scan > Scheduled
2. Edit the discovery
3. Open the Speed tab
4. Re-apply your scan rate, ARP rate, and other speed settings

3. Update API integrations

If you have API integrations that create or reference credentials, the SNMP credential type discriminant changed:

Update any code that creates credentials or filters by credential type. The version selector field has been removed — the type name now includes the version.

New Features in v0.15.0

Credential wizard

When creating a new daemon or editing an existing discovery, a Credentials tab lets you add SNMP and Docker Proxy credentials with target IPs. Credentials are auto-assigned to discovered hosts after the first scan. See Credentials for details.

Docker mode selection

During daemon setup, you can now choose how Docker discovery works:

• Disabled — no Docker scanning
• Local Socket — scan containers via the local Docker socket (default)
• Proxy — scan containers via a remote Docker Proxy credential

Scan lifecycle

Discovery now alternates between light and deep scans on a configurable interval. See Discovery — Scanning Lifecycle for how scan depth works.

Remote Docker scanning

Docker Proxy credentials can point to any reachable Docker API endpoint, enabling container discovery on remote hosts — not just the daemon's own host.

Deprecation Timeline