Method for adapting to Podman calling by improving Docker Api, terminal equipment and storage medium

Abstract

The invention relates to a method for adapting to Podman calling by improving Docker Api, terminal equipment and a storage medium, and the method comprises the following steps: according to different types of accessed podman and docker containers, modifying a Unix socket path of a docker default connection; when the type of the accessed container is podman, after a dockerapai is called to execute a command in the container, aiming at message data contained in a returned execution result, analyzing by adopting an analysis mode different from that of dockee; and when the type of the accessed container is podman, when the dockerapai is called to obtain process information in the podman container, removing a space character between a parameter-axo and a stat in a top interface provided by the dockerapai. According to the method and the device, certain transformation is carried out on the docker, so that the transformed docker can use container environments of the docker and the podman at the same time, and the workload of secondary development of the docker and the podman and obtaining of container information through remote management of the docker and the podman is reduced.

Description

technical field [0001] The invention relates to the technical field of containers, in particular to a method for invoking Podman by improving DockerApi, a terminal device and a storage medium. Background technique [0002] As an open source container runtime project, Podman can be used on most Linux platforms. Podman provides functions very similar to Docker. The earlier version of PodmanApi was designed using the VarLink protocol. The new version implements Api in a similar way to Docker (both adopt the Http rest API method). However, since Podman started relatively late, the official API only provides a relatively basic calling interface. , and most of the call interfaces only provide a function interface, and then directly throw an exception that the interface has not yet been implemented. As a result, if the existing official API is directly called, most of the interfaces cannot be implemented. If podman implements all the api interfaces in the later stage, it will also...

AI Technical Summary

Problems solved by technology

The earlier version of PodmanApi was designed using the VarLink protocol. The new version implements Api in a similar way to Docker (both adopt the Http rest API method). However, since Podman started relatively late, the official API only provides a relatively basic calling interface. , and most of the call interfaces only provide a function interface, and then directly throw an exception that the interface has not yet been implemented. As a result, if the existing official API is directly called, most of the interfaces cannot be implemented.

If podman implements all the api interfaces in the later stage, it will also operate the docker container because of the docker api used by the user. If the new operation of podman is added, the podman library will be introduced, and the names of the two sets of library function interfaces are quite different, and the calling methods are also very different. Big, the workload is relatively large to transform

Images