The developers announced the first release "Podman 2", a major update of the podman project – a utility for creating, running, and managing containers according to the OCI. Podman is an alternative to Docker and allows management of containers without a background system service and without requiring root privileges.
For end users, the changes will be almost invisible, but in some cases, the format of the JSON data will change.
The main distinction of the second version is a fully functional REST API. An experimental implementation of the API based on varlink was available in the first branch, but in the new version, it has been completely reworked. Instead of a varlink interface, a standard HTTP API is now used.
The new REST API has two layers: an interface to the functions of the libpod library and a compatibility layer that partially implements Docker API functions. For new applications, it is advisable to use the 'native' libpod interface.
The new REST API has significantly reduced the size of the podman client application for Mac and Windows.
Key Changes:
- The REST API and podman system service are no longer considered experimental and are ready for use.
- The podman command can connect to a remote podman service using the --remote flag.
- The podman client has been completely rewritten and now uses the HTTP API instead of Varlink.
- A podman system connection command has been added for configuring remote connections that are then used by the podman-remote and podman --remote commands.
- The podman generate systemd command now supports the --new flag and can create systemd services for pods.
- The podman play kube command supports the launching of Kubernetes deployment objects.
- The podman exec command has received the --detach flag to run commands in the background.
- The -p flag for the podman run and podman create commands now supports port forwarding to IPv6 addresses.
- The podman run, podman create, and podman pod commands now support the --replace flag to recreate a container with the same name.
- The --restart-policy flag for the podman run and podman create commands now supports the unless-stopped policy.
- The --log-driver flag for the podman run and podman create commands can accept the none value, which disables container logging.
- The podman generate systemd command accepts arguments --container-prefix, --pod-prefix, and --separator that control the created units.
- The podman network ls command supports the --filter flag to filter results.
- The podman auto-update command supports specifying an authfile for the container.
Source: linux.org.ru
