The developers announced the first release "Subman 2", a major update of the podman project - a utility for creating, running and managing containers of the standard LEISURE. Podman is an alternative to the Docker project and allows you to manage containers without having a background system service and without requiring root rights.
For the end user, the changes will be almost imperceptible, however, in some cases, the json data format will change.
The main difference of the second version is a fully functional REST API. An experimental implementation of the varlink-based API was also available in the first branch, but it has been completely redesigned in the new version. The standard HTTP API is now used instead of the varlink interface.
The new REST API has two layers: an interface to the libpod library functions and a compatibility layer that partially implements the Docker API functions. For new applications, of course, it is recommended to use the native libpod interface.
The new REST API has significantly reduced the size of the podman client application for Mac and Windows.
Major changes:
- The REST API and podman system service are no longer considered experimental and are ready to 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.
- Added podman system connection command to configure remote connections, which are then used by the podman-remote and podman --remote commands.
- The podman generate systemd command now supports the --new flag, and can generate systemd services for pods.
- The podman play kube command supports running Kubernetes deployment objects.
- The podman exec command received a --detach flag to execute 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 be set to none, which disables container logging.
- The podman generate systemd command accepts --container-prefix, --pod-prefix, and --separator arguments that control the units that are generated.
- The podman network ls command supports a --filter flag to filter out results.
- The podman auto-update command supports specifying an authfile for a container.
Source: linux.org.ru