mirror of https://github.com/podman-desktop/podman-desktop synced 2026-04-21 17:47:22 +00:00

docs: add information regarding registries.defaults (#15075 )

### What does this PR do?

Adds documentation regarding the new settings.json feature being added.

This gives us documentation on it, the upstream (Podman documentation)
references, as well as a managed-by example on how to use it.

### Screenshot / video of UI

N/A

### What issues does this PR fix or reference?

Closes https://github.com/podman-desktop/podman-desktop/issues/15004

### How to test this PR?

N/A, documentation.

Signed-off-by: Charlie Drage <charlie@charliedrage.com>

2025-12-03 20:24:26 +00:00

3.6 KiB

Raw Blame History

sidebar_position

title

description

Managed configuration use cases

As an administrator, you can use managed configuration to enforce specific settings for all users in your organization. Below are some common use cases with example configurations.

Enforcing proxy settings

Lock proxy configuration to ensure all users route traffic through corporate proxy servers.

{
  "proxy.http": "http://corp-proxy.example.com:8080"
}

{
  "locked": ["proxy.http"]
}

Managing telemetry

Control telemetry settings for compliance or privacy requirements.

{
  "telemetry.enabled": false
}

{
  "locked": ["telemetry.enabled"]
}

Configuring default registries and mirrors

Configure default container registries with optional mirrors for your organization. This is useful for directing image pulls through internal registry mirrors or blocking access to specific registries.

Each entry in the registries.defaults array can be either a registry definition or a mirror. Mirrors must follow immediately after the registry they belong to.

:::note This configuration maps to the registries.conf format used by Podman. For advanced configuration options and detailed documentation, refer to the upstream specification on how to setup your registries.conf and how Podman Desktop reads/writes to it. :::

Registry properties

Property	Type	Required	Description
`prefix`	string	Yes	The registry prefix to match (e.g., `quay.io`)
`location`	string	Yes	The registry URL or location
`insecure`	boolean	No	Allow insecure connections (default: `false`)
`blocked`	boolean	No	Block pulls (default: `false`)

Mirror properties

Property	Type	Required	Description
`location`	string	Yes	The mirror URL
`insecure`	boolean	No	Allow insecure connections (default: `false`)

Example: Configure a registry with a mirror

{
  "registries.defaults": [
    {
      "registry": {
        "prefix": "quay.io",
        "location": "quay.io"
      }
    },
    {
      "registry.mirror": {
        "location": "mirror.example.com"
      }
    }
  ]
}

Example: Block a registry

{
  "registries.defaults": [
    {
      "registry": {
        "prefix": "untrusted.example.com",
        "location": "untrusted.example.com",
        "blocked": true
      }
    }
  ]
}

3.6 KiB Raw Blame History