# podman

* [Config](#config)
* [CLI](#cli)
* [network](#network)
  * [Netavark](#netavark)
  * [CNI](#cni)
    * [DHCP](#dhcp)
  * [create](#create)

## Config

V2: /etc/containers/registries.conf

```
unqualified-search-registries = ["docker.io"]
```

## CLI

```
podman search docker.io/KEYWORD
```

## network

<https://docs.podman.io/en/latest/markdown/podman-network.1.html>

* Netavark is the default network backend and was added in Podman v4.0
* CNI will be deprecated

<https://github.com/containers/common/blob/main/docs/containers.conf.5.md#network-table>

/etc/containers/containers.conf

```
[network]
network_backend="" # cni / netavark
```

```
podman network inspect podman
```

### Netavark

<https://www.redhat.com/sysadmin/podman-new-network-stack>

* Better IPv6 support
* Improved support for containers in multiple networks
* Improved performance

### CNI

cni\_config\_dir in containers.conf: /etc/cni/net.d

DHCP: <https://www.cni.dev/plugins/v0.8/ipam/dhcp/>

### create

<https://docs.podman.io/en/latest/markdown/podman-network-create.1.html>

`--driver`

* bridge
* macvlan
* ipvlan

`--ipam-driver`

* dhcp: not yet supported with netavark | For CNI the dhcp plugin needs to be activated before.
* host-local
* none


---

# Agent Instructions: Querying This Documentation

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

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://book.ferro.pro/container/podman.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.