CN115658217A - Container application processing method, electronic device and computer-readable storage medium - Google Patents
Container application processing method, electronic device and computer-readable storage medium Download PDFInfo
- Publication number
- CN115658217A CN115658217A CN202211077120.2A CN202211077120A CN115658217A CN 115658217 A CN115658217 A CN 115658217A CN 202211077120 A CN202211077120 A CN 202211077120A CN 115658217 A CN115658217 A CN 115658217A
- Authority
- CN
- China
- Prior art keywords
- image file
- application
- target
- mirror
- container
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Pending
Links
Images
Landscapes
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The application discloses a container application processing method, an electronic device and a computer readable storage medium. The method comprises the following steps: acquiring an identifier of a container application to be processed; determining an incremental image file corresponding to the identifier from the image warehouse based on the identifier; and updating the application of the container to be processed by utilizing the incremental image file. By the method, the updating efficiency of the application of the container to be processed can be improved, and the resource occupation in the updating process is reduced.
Description
Technical Field
The present application relates to the field of container application processing technologies, and in particular, to a container application processing method, an electronic device, and a computer-readable storage medium.
Background
With the vigorous development of domestic cloud computing technology, more and more business scenes covered by release based on virtualization and containerization technology are provided, but in the aspect of current service application deployment, deployed objects are a pile of output products of Jar, WAR, DLL and other program codes, all servers are different, and a generation environment, a quasi-production environment and a development environment have natural difference, so that the deployment difficulty and the project uncontrollable property are greatly increased.
Disclosure of Invention
The application provides a container application processing method, an electronic device and a computer readable storage medium, which can improve the updating efficiency of a container application to be processed and reduce the resource occupation in the updating process.
In a first aspect, the present application provides a method for processing a container application, the method comprising: acquiring an identifier of a container application to be processed; determining an incremental image file corresponding to the identifier from the image warehouse based on the identifier; and updating the application of the container to be processed by utilizing the incremental image file.
Wherein, the determining of the incremental image file corresponding to the identifier from the image warehouse based on the identifier comprises: acquiring original template information of the application of the container to be processed by using the identifier; acquiring target template information corresponding to the application of the container to be processed from a mirror image warehouse; determining incremental information by using the original template information and the target template information; and obtaining the incremental image file based on the incremental information.
The method for acquiring the target template information corresponding to the application of the container to be processed from the mirror image warehouse comprises the following steps: providing a display interface, wherein the display interface is used for displaying at least one target container application identifier; and responding to the selection of any target container application identifier, and acquiring target template information corresponding to the target container application identifier from the mirror repository.
The container application comprises a plurality of sub-applications, and the template information comprises at least one of the version number of each sub-application, the dependency relationship among the sub-applications or the configuration parameters of the sub-applications; determining incremental information by using the original template information and the target template information, wherein the incremental information comprises the following steps: acquiring a target version number of the sub-applications, a target dependency relationship among the sub-applications or a target configuration parameter of the sub-applications in the target template information; acquiring an original version number of the sub-applications in the original template information, original dependency relationships among the sub-applications or original configuration parameters of the sub-applications; and comparing the target version number, the target dependency relationship, the target configuration parameters with the original version number, the original dependency relationship and the original configuration parameters to determine incremental information.
The obtaining of the incremental image file based on the incremental information includes: generating mirror image file information based on the incremental information; acquiring a target mirror image file corresponding to the mirror image file information from a mirror image warehouse; and taking the target image file as an incremental image file.
Wherein, updating the application of the container to be processed by using the incremental image file comprises the following steps: and updating the application of the container to be processed by utilizing the increment mirror image file, and taking the target template as an original template.
The mirror image warehouse comprises a first mirror image warehouse, a second mirror image warehouse and a third mirror image warehouse; the first mirror image warehouse is used for storing a first mirror image file formed by the container application in a development stage; the second mirror image warehouse is used for storing a second mirror image file formed by the container application in the testing stage; the second image file is obtained by testing part of the first image file; the third mirror image warehouse is used for storing a third mirror image file formed by the container application in the release stage; the third image file is obtained by screening part of the second image files; determining an incremental image file corresponding to the identifier from the image warehouse based on the identifier, including: and determining a third image file corresponding to the identifier from the third image warehouse based on the identifier, and taking the third incremental file as an incremental image file.
The storage period of the third mirror image file by the third mirror image warehouse is greater than that of the second mirror image file by the second mirror image warehouse, and the storage period of the second mirror image file by the second mirror image warehouse is greater than that of the first mirror image file by the first mirror image warehouse.
In a second aspect, the present application provides an electronic device comprising a processor and a memory coupled to the processor; wherein the memory is adapted to store a computer program and the processor is adapted to execute the computer program to implement the method as provided in the first aspect.
In a third aspect, the present application provides a computer readable storage medium storing a computer program which, when executed by a processor, implements the method as provided in the first aspect.
The beneficial effect of this application is: different from the situation of the prior art, the container application processing method, the electronic device and the computer-readable storage medium provided by the application can be used for rapidly extracting the incremental image file with less data amount by determining the incremental image file corresponding to the identifier from the image warehouse based on the identifier, without acquiring the full amount of image files from the image warehouse, and updating the container application to be processed by using the incremental image file, so that the updating efficiency of the container application to be processed is improved, and the resource occupation in the updating process is reduced.
Drawings
In order to more clearly illustrate the technical solutions in the embodiments of the present application, the drawings needed to be used in the description of the embodiments are briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present application, and it is obvious for those skilled in the art to obtain other drawings based on these drawings without creative efforts.
Wherein:
FIG. 1 is a schematic flow chart diagram of a first embodiment of a method for processing a container application provided herein;
FIG. 2 is a schematic flow chart diagram of a second embodiment of a method for processing a container application provided herein;
FIG. 3 is a schematic diagram of an application scenario of a processing method of a container application provided in the present application;
FIG. 4 is a schematic flow chart diagram illustrating one embodiment of step 24 provided herein;
FIG. 5 is a schematic flow chart diagram illustrating an embodiment of step 25 provided herein;
FIG. 6 is a schematic flow chart diagram of a third embodiment of a method for processing a container application provided herein;
FIG. 7 is a schematic structural diagram of an embodiment of an electronic device provided in the present application;
FIG. 8 is a schematic structural diagram of an embodiment of a computer-readable storage medium provided in the present application.
Detailed Description
The technical solutions in the embodiments of the present application will be clearly and completely described below with reference to the drawings in the embodiments of the present application. It is to be understood that the specific embodiments described herein are merely illustrative of the application and are not limiting of the application. It should be further noted that, for the convenience of description, only some of the structures associated with the present application are shown in the drawings, not all of them. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present application.
Reference herein to "an embodiment" means that a particular feature, structure, or characteristic described in connection with the embodiment can be included in at least one embodiment of the application. The appearances of the phrase in various places in the specification are not necessarily all referring to the same embodiment, nor are separate or alternative embodiments mutually exclusive of other embodiments. It is explicitly and implicitly understood by one skilled in the art that the embodiments described herein can be combined with other embodiments.
The following terms are explained here:
container mirroring: one of the products after the business containerization comprises business program information, program dependency relationship and the like.
Applying a template: one of the products after business containerization contains configuration information of business microservices, such as resource configuration, copy number, affinity, and the like.
The application of the container comprises the following steps: and the object after the business containerization can deploy the running business on the container based on the object.
With the vigorous development of domestic cloud computing technology, more and more business scenes covered by release based on virtualization and containerization technology are provided, but in the aspect of current service application deployment, deployed objects are a pile of output products of Jar, WAR, DLL and other program codes, all servers have difference, and the generation environment, the quasi-production environment and the development environment have natural difference, so that the deployment difficulty and the project uncontrollable property are greatly increased.
The inventor has long studied and found that the release of the current container application is basically performed in a compressed package from the product dimension, and because of the lack of incremental management, the container application is cured and stored in full amount each time, which causes serious waste to resources and is very inefficient.
Based on this problem, the present application proposes any of the following embodiments to solve the above problem.
Referring to fig. 1, fig. 1 is a schematic flow chart of a first embodiment of a processing method for a container application provided in the present application. The method comprises the following steps:
step 11: and acquiring the identifier of the application of the container to be processed.
In some embodiments, the identifier of the container application has uniqueness, and the related information of the container application can be determined based on the identifier. Wherein the identification may be an ID of the container application to be processed.
In some embodiments, a display interface is provided for displaying an identification of at least one pending container application; in response to selection of any of the identifiers, it is then determined that the container application to which the identifier corresponds requires processing.
Step 12: and determining the incremental image file corresponding to the identifier from the image warehouse based on the identifier.
The container application system comprises a container application, a container storage and a mirror image warehouse, wherein a plurality of mirror image files are stored in the mirror image warehouse, and each mirror image file corresponds to the container application. That is, multiple image files in the image repository may correspond to multiple container applications. In other words, different container applications may have different image files depending on the version number.
In some embodiments, the related information of the container application to be processed, such as the name, version number, etc. of the container application to be processed, may be determined based on the identifier. Then, based on the name of the container application to be processed, the corresponding target container application in the mirror repository is determined.
A delta image file is then determined based on the image file of the target container application.
The incremental image file may be an image file newly added to the target container application when the to-be-processed container application is compared with the target container application, that is, an image file not included in the to-be-processed container application.
The delta file may be an image file deleted from the target container application when the to-be-processed container application is compared with the target container application, that is, an image file existing in the to-be-processed container application and not existing in the target container application.
The delta file may be an image file modified in the target container application when the pending container application is compared with the target container application, that is, the image file exists in the pending container application, but the image file is changed in the target container application, for example, the image file is modified.
That is, at step 12, a plurality of delta image files may be determined.
Step 13: and updating the application of the container to be processed by utilizing the incremental image file.
In some embodiments, the application of the container to be processed is updated and then the container can be directly deployed for use.
In some embodiments, if the incremental image file is a newly added image file, the incremental image file may be directly inserted into an original image file applied to the container to be processed, and a corresponding relationship between the incremental image file and the original image file is established.
In some embodiments, if the incremental image file is a deleted image file, the original image file corresponding to the deleted image file may be determined from the to-be-processed container application, the original image file may be deleted, and a correspondence relationship between existing original image files may be established.
In some embodiments, if the incremental image file is a modified image file, an original image file corresponding to the modified image file may be determined from the application of the container to be processed, the modified image file is used to replace the original image file, and a correspondence relationship between the replaced image file and other original image files is established.
In some embodiments, a plurality of incremental image files are determined, and the application of the container to be processed is updated according to the above process according to the characteristics of each incremental image file. Wherein, the property of the incremental image file can be new, deleted or modified.
In an application scene, by the above mode, after the application of the to-be-processed container is updated, the updated application of the to-be-processed container can be directly deployed on the cloud server.
In another application scenario, the application of the to-be-processed container in the cloud server needs to be updated, and then the application of the to-be-processed container in the cloud server can be updated in the above manner.
In this embodiment, the incremental image file corresponding to the identifier is determined from the image warehouse based on the identifier, so that the incremental image file with a small data amount can be quickly extracted, the full-scale image file does not need to be acquired from the image warehouse, and the application of the container to be processed is updated by using the incremental image file, thereby improving the updating efficiency of the application of the container to be processed and reducing the resource occupation in the updating process.
Referring to fig. 2, fig. 2 is a schematic flow chart of a second embodiment of a processing method for a container application provided in the present application. The method comprises the following steps:
step 21: an identification of a container application to be processed is obtained.
Step 22: and acquiring the original template information of the container application to be processed by using the identifier.
In some embodiments, the container application may have a plurality of sub-applications, and thus, the template information includes information such as a version number of the sub-application, a dependency relationship between the sub-applications, and a configuration parameter of the sub-application.
In other embodiments, the template information further includes a list of image files for the container application. The image file list includes information of image files constituting the container application. Such as the name, version number, etc. of the image file.
Step 23: and acquiring target template information corresponding to the application of the container to be processed from the mirror image warehouse.
In some embodiments, different versions of the container application and corresponding target information are stored in the mirror repository. Therefore, after the target container application in the mirror repository is determined, the target template information corresponding to the target container application can be acquired.
In some embodiments, a display interface is provided for displaying at least one target container application identifier; and responding to the selection of any target container application identifier, and acquiring target template information corresponding to the target container application identifier from the mirror repository.
The description is made with reference to fig. 3:
as shown in fig. 3, a target container application identifier a, a target container application identifier B, a target container application identifier C, a target container application identifier D, a target container application identifier E, a target container application identifier F, a target container application identifier G, and a target container application identifier H are displayed. Each target container application identification corresponds to a target container application in a mirror repository. The target container application identifier may be a release file number corresponding to the target container application.
And responding to the selection of any target container application identifier, and acquiring target template information corresponding to the target container application identifier from the mirror repository. And if the target container application identifier A is selected, acquiring target template information corresponding to the target container application identifier A from the mirror image warehouse.
Step 24: and determining incremental information by using the original template information and the target template information.
In some embodiments, the check value may be utilized to determine the incremental information. For example, after the image file is generated, a check value is correspondingly generated. E.g., using MD5 values. That is, if the image file is modified, the check value is different from the previous check value, and the corresponding incremental image file information in the target container application can be determined according to the check value.
In some embodiments, the container application includes a plurality of sub-applications, and the template information includes at least one of a version number of each sub-application, a dependency relationship between the sub-applications, or a configuration parameter of the sub-application. Referring to fig. 4, step 24 may be the following process:
step 41: and acquiring the target version number of the sub-applications, the target dependency relationship among the sub-applications or the target configuration parameters of the sub-applications in the target template information.
Step 42: and acquiring the original version number of the sub-applications, the original dependency relationship among the sub-applications or the original configuration parameters of the sub-applications in the original template information.
Step 43: and comparing the target version number, the target dependency relationship, the target configuration parameters with the original version number, the original dependency relationship and the original configuration parameters to determine incremental information.
If the target version number is different from the original version number, which indicates that the sub-application corresponding to the target version number is modified, the image file of the sub-application corresponding to the target version number may be used as the incremental information.
If the target dependency relationship is different from the original dependency relationship, which indicates that the dependency relationship between the sub-applications has changed, the image file of the sub-application corresponding to the target dependency relationship may be used as the incremental information.
If the target configuration parameter is different from the original configuration parameter, which indicates that the configuration parameter has changed, the image file of the sub-application corresponding to the configuration parameter may be used as the incremental information.
The version number, the dependency relationship and the configuration parameters are interactive, if the version number changes, it is indicated that the image file is modified, and if the image file is modified, the dependency relationship and the configuration parameters can change, so that the version number, the dependency relationship and the configuration parameters can be compared integrally to determine the incremental information.
Step 25: and obtaining the incremental image file based on the incremental information.
In some embodiments, referring to fig. 5, step 25 may be the following flow:
step 51: and generating image file information based on the incremental information.
The incremental information may be image file information corresponding to an image file, and thus may also be changed into an image package in a packaging manner. It is understood that the mirror package is also a mirror file.
The image file information may be a name of the image file and/or a storage path of the image file, a version number of the image file, and the like.
Step 52: and acquiring a target image file corresponding to the image file information from the image warehouse.
And determining the image file information in the image package by reading the image package, and further acquiring a target image file corresponding to the image file information from the image warehouse.
Step 53: and taking the target image file as an incremental image file.
The target image file acquired at this time may be used as an incremental image file.
Step 26: and updating the application of the container to be processed by utilizing the incremental image file.
In some embodiments, the application of the container to be processed is updated with the delta image file, with the target template as the original template.
After the application of the container to be processed is updated, the original template before the application of the container to be processed is updated does not correspond to the application of the container to be processed after the application of the container to be processed is updated naturally, so that the target template is used as the original template.
In this embodiment, the incremental image file corresponding to the identifier is determined from the image warehouse based on the identifier, so that the incremental image file with a small data amount can be quickly extracted, the full-scale image file does not need to be acquired from the image warehouse, and the application of the container to be processed is updated by using the incremental image file, thereby improving the updating efficiency of the application of the container to be processed and reducing the resource occupation in the updating process.
In some embodiments, the mirror repositories include a first mirror repository, a second mirror repository, and a third mirror repository; the first mirror image warehouse is used for storing a first mirror image file formed by the container application in the development stage; the second mirror image warehouse is used for storing a second mirror image file formed by the container application in the testing stage; the second image file is obtained by testing part of the first image file; the third mirror image warehouse is used for storing a third mirror image file formed by the container application in the release stage; and the third image file is obtained by screening part of the second image file.
The determining, based on the identifier, the incremental image file corresponding to the identifier from the image repository in the foregoing embodiment may be determining, based on the identifier, a third image file corresponding to the identifier from a third image repository, and using the third incremental file as the incremental image file.
Referring to fig. 6, fig. 6 is a schematic flow chart of a third embodiment of a processing method for a container application provided in the present application. The method comprises the following steps:
step 61: and manufacturing a first image file corresponding to the container application, and storing the first image file in a first image warehouse.
In the development stage, different versions of container applications are developed according to customer requirements. I.e., the first image file corresponding to a different version.
The synchronization forms template information when the corresponding first image file of the container application is made. Thus, the first image file and the template information are stored in a first image repository.
The first mirror image warehouse has low requirement on the storage period, and the first mirror image file in the first mirror image warehouse can be deleted and replaced for storage in a circulating coverage mode in the development process, so that the storage efficiency can be improved, and the storage resources can be saved. Can be rebuilt at any time based on the tag label of the code repository.
Step 62: and acquiring part of the first image file from the first image warehouse, storing the part of the first image file in the second image warehouse, and testing the part of the first image file to obtain a second image file.
After the first image repository stores the first image file, a part of the first image file is tested, and then a part of the first image file can be stored in the second image repository.
Isolation exists between the first mirror repository and the second mirror repository. I.e., the first mirror repository and the second mirror repository cannot communicate with each other.
Different mirror image warehouses are used for storing the mirror image files, and the uniqueness and the integrity of the mirror image files can be guaranteed after the first mirror image warehouse is isolated.
In the second mirror image warehouse, the storage period of the mirror image file is prolonged to a certain extent compared with that of the first mirror image warehouse; meanwhile, the number of the mirror image files is further reduced through flow limitation, and if the number of the mirror image files can be controlled to be lower than one tenth of that of the first mirror image warehouse, storage resources can be saved by more than 10 times.
And step 63: and acquiring part of the second image file from the second image warehouse, and storing the part of the second image file as a third image file in a third image warehouse.
After the test is finished, part of the second image files meeting the release requirement can be deleted and selected for release, so that part of the second image files are obtained from the second image warehouse and stored in the third image warehouse as third image files.
The third mirror image file in the third mirror image warehouse is not allowed to be modified and is kept isolated from the first mirror image warehouse and the second mirror image warehouse so as to keep the consistency of the mirror image file in the mirror image warehouse; meanwhile, the storage period of the third mirror image warehouse requires that the mirror image file is permanently reserved before the mirror image file is abandoned. That is, the storage period of the third mirror image file by the third mirror image warehouse is longer than the storage period of the second mirror image file by the second mirror image warehouse, and the storage period of the second mirror image file by the second mirror image warehouse is longer than the storage period of the first mirror image file by the first mirror image warehouse.
Through the mode, the data volume of the mirror image file in the third mirror image warehouse can be reduced by 4-5 times compared with the data in the second mirror image warehouse.
In the embodiment, a three-level storage mode (the first mirror image warehouse, the second mirror image warehouse and the third mirror image warehouse) is used for accessing the mirror image files, so that the traceability and uniqueness of the tested and issued mirror image files are guaranteed, meanwhile, the multi-level hierarchical storage design can effectively improve the storage efficiency, and the storage resources are saved by more than 10 times.
In an application scenario, the image file in the third image repository may be deployed. For example, when the container application is deployed for the first time, all image files of the container application in the third image repository may be directly loaded, so that deployment and subsequent operation of the container application are realized.
When the deployed container application needs version iteration, the identifier of the deployed container application can be acquired, and the image list and the template information of the deployed container application are acquired through the identifier of the deployed container application, wherein the template information comprises information such as version numbers, dependency relationships among applications, configuration parameters and the like.
And acquiring a mirror image list and template information of the corresponding target container application in the third mirror image warehouse.
And determining differential image file information, namely corresponding to the incremental image file, by comparing the image list and the template information of the deployed container application with the image list and the template information of the target container application.
For example, the schema file of the template information of the deployed container application and the template information of the target container application are compared to produce a difference digest file. Specifically, the schema file may be transferred into a registration interface, a difference digest file is returned by comparison, and the difference is stored as layer.
And then, building a mirror image package according to rules through the difference digest file. For example, the difference rule data is generated by the difference digest file and the layers data: the method comprises the steps that mirror image names, versions and layers are arranged, different layer files are placed in different directories, the names of folders in the same incremental downloading process are only packaged into mirror image packages by using a tar command according to relevant rules.
And then downloading the image file from the third image warehouse according to the image package.
If so, downloading the difference image file diff _ image.tar from the third image repository according to the image package, then internally calling docker load < diff _ image.tar > to import the difference image file, and executing the upgrade operation to finish the use of differential image loading.
Referring to fig. 7, fig. 7 is a schematic structural diagram of an embodiment of an electronic device provided in the present application. The electronic device 70 comprises a processor 71 and a memory 72 coupled to the processor 71; wherein the memory 72 is adapted to store a computer program and the processor 71 is adapted to execute the computer program to implement the following method:
acquiring an identifier of a container application to be processed; determining an incremental image file corresponding to the identifier from the image warehouse based on the identifier; and updating the application of the container to be processed by utilizing the incremental image file.
It will be appreciated that the processor 71 is also arranged to execute a computer program to implement any of the methods of the implementations described above.
Referring to fig. 8, fig. 8 is a schematic structural diagram of an embodiment of a computer-readable storage medium provided in the present application. The computer-readable storage medium 80 stores a computer program 81, the computer program 81, when executed by a processor, implementing the method of:
acquiring an identifier of a container application to be processed; determining an incremental image file corresponding to the identifier from the image warehouse based on the identifier; and updating the application of the container to be processed by utilizing the incremental image file.
It will be appreciated that the computer program 81, when executed by a processor, is also for implementing any of the methods embodied above.
To sum up, this application can extract the less increment image file of data volume fast through determining the increment image file that corresponds with the sign from the image warehouse based on the sign, need not to obtain the full amount image file from the image warehouse, and utilizes the increment image file to treat the processing container and use and update, promotes the update efficiency of treating the processing container and use, reduces the resource occupation of update in-process.
Furthermore, a three-level storage mode (a first mirror image warehouse, a second mirror image warehouse and a third mirror image warehouse) is used for accessing the mirror image files, so that the traceability and the uniqueness of the tested and issued mirror image files are guaranteed, the multi-level hierarchical storage design can effectively improve the storage efficiency, and the storage resources are saved by more than 10 times.
In the several embodiments provided in the present application, it should be understood that the disclosed method and apparatus may be implemented in other manners. For example, the above-described device embodiments are merely illustrative, and for example, the division of the modules or units is only one logical division, and other divisions may be realized in practice, for example, a plurality of units or components may be combined or integrated into another system, or some features may be omitted, or not executed.
The integrated units in the other embodiments described above may be stored in a computer-readable storage medium if they are implemented in the form of software functional units and sold or used as separate products. Based on such understanding, the technical solution of the present application may be substantially implemented or contributed by the prior art, or all or part of the technical solution may be embodied in a software product, which is stored in a storage medium and includes instructions for causing a computer device (which may be a personal computer, a server, a network device, or the like) or a processor (processor) to execute all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a Read-Only Memory (ROM), a Random Access Memory (RAM), a magnetic disk or an optical disk, and other various media capable of storing program codes.
The above description is only for the purpose of illustrating embodiments of the present application and is not intended to limit the scope of the present application, and all modifications of equivalent structures and equivalent processes, which are made by the contents of the specification and the drawings of the present application or are directly or indirectly applied to other related technical fields, are also included in the scope of the present application.
Claims (10)
1. A method of processing a container application, the method comprising:
acquiring an identifier of a container application to be processed;
determining an incremental image file corresponding to the identifier from an image warehouse based on the identifier;
and updating the application of the container to be processed by utilizing the incremental image file.
2. The method of claim 1, wherein determining the incremental image file corresponding to the identifier from the image repository based on the identifier comprises:
acquiring original template information of the container application to be processed by using the identifier;
acquiring target template information corresponding to the application of the container to be processed from a mirror image warehouse;
determining incremental information by using the original template information and the target template information;
and obtaining the incremental mirror image file based on the incremental information.
3. The method according to claim 2, wherein the obtaining target template information corresponding to the application of the container to be processed from a mirror repository comprises:
providing a display interface, wherein the display interface is used for displaying at least one target container application identifier;
and responding to the selection of any target container application identifier, and acquiring target template information corresponding to the target container application identifier from the mirror repository.
4. The method of claim 2, wherein the container application comprises a plurality of sub-applications, and the template information comprises at least one of a version number of each sub-application, a dependency relationship between the sub-applications, or a configuration parameter of the sub-application;
determining incremental information by using the original template information and the target template information, including:
acquiring a target version number of the sub-applications, a target dependency relationship among the sub-applications or a target configuration parameter of the sub-applications in the target template information;
acquiring an original version number of the sub-applications in the original template information, original dependency relationships among the sub-applications or original configuration parameters of the sub-applications;
and comparing the target version number, the target dependency relationship, the target configuration parameters with the original version number, the original dependency relationship and the original configuration parameters to determine the incremental information.
5. The method of claim 2, wherein obtaining the incremental image file based on the incremental information comprises:
generating mirror image file information based on the incremental information;
acquiring a target image file corresponding to the image file information from the image warehouse;
and taking the target image file as the increment image file.
6. The method of claim 2, wherein the updating the container application to be processed with the delta image file comprises:
and updating the application of the container to be processed by using the increment image file, and taking the target template as the original template.
7. The method of claim 1, wherein the mirror repositories include a first mirror repository, a second mirror repository, and a third mirror repository;
the first mirror image warehouse is used for storing a first mirror image file formed by the container application in a development stage;
the second mirror image warehouse is used for storing a second mirror image file formed by the container application in a testing stage; the second image file is obtained by testing part of the first image file;
the third mirror image warehouse is used for storing a third mirror image file formed by the container application in a release stage; the third image file is obtained by screening part of the second image files;
the determining, from the mirror repository based on the identifier, an incremental mirror file corresponding to the identifier includes:
and determining a third image file corresponding to the identifier from the third image warehouse based on the identifier, and taking the third incremental file as the incremental image file.
8. The method of claim 7,
the storage period of the third mirror image warehouse for the third mirror image file is longer than that of the second mirror image warehouse for the second mirror image file, and the storage period of the second mirror image warehouse for the second mirror image file is longer than that of the first mirror image warehouse for the first mirror image file.
9. An electronic device comprising a processor and a memory coupled to the processor;
wherein the memory is adapted to store a computer program and the processor is adapted to execute the computer program to implement the method according to any of claims 1-8.
10. A computer-readable storage medium, characterized in that the computer-readable storage medium stores a computer program which, when executed by a processor, implements the method of any one of claims 1-8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211077120.2A CN115658217A (en) | 2022-09-01 | 2022-09-01 | Container application processing method, electronic device and computer-readable storage medium |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202211077120.2A CN115658217A (en) | 2022-09-01 | 2022-09-01 | Container application processing method, electronic device and computer-readable storage medium |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN115658217A true CN115658217A (en) | 2023-01-31 |
Family
ID=84983873
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202211077120.2A Pending CN115658217A (en) | 2022-09-01 | 2022-09-01 | Container application processing method, electronic device and computer-readable storage medium |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN115658217A (en) |
-
2022
- 2022-09-01 CN CN202211077120.2A patent/CN115658217A/en active Pending
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| EP1582985B1 (en) | Test case inheritance controlled via attributes | |
| US20100293538A1 (en) | Dynamic program updating in a continuation based runtime | |
| CN104714812A (en) | Method and system for quickly deploying and loading Java applications in cloud environment | |
| CN106557307B (en) | Service data processing method and system | |
| CN115993966B (en) | Application development system and method | |
| CN115658085A (en) | Deployment method of cloud native application | |
| CN112965936A (en) | Processing method, device, equipment and storage medium of heterogeneous distributed model | |
| CN113157315A (en) | Method, device, equipment and medium for identifying difference information of different versions of software | |
| CN112328241B (en) | Method and device for creating Android library module dependency relationship in application program development | |
| CN113296891A (en) | Multi-scene knowledge graph processing method and device based on platform | |
| CN115576903B (en) | File system construction method, computing device and storage medium | |
| CN115658217A (en) | Container application processing method, electronic device and computer-readable storage medium | |
| CN116578287A (en) | Service processing method, intelligent terminal and storage medium | |
| CN115729590A (en) | Service deployment method, device, equipment and computer readable storage medium | |
| CN112691382B (en) | Resource processing method, device and computer readable storage medium | |
| CN114579142A (en) | Dual-mode big data version deployment method, device and equipment supporting steady state and sensitive state | |
| CN116954878A (en) | Method, apparatus, device, storage medium and program product for managing container clusters | |
| CN112667491A (en) | Function test method and device of virtual machine | |
| CN111737964A (en) | Form dynamic processing method, equipment and medium | |
| CN108573142B (en) | Method and device for realizing hook | |
| CN114398073B (en) | Application updating method and device based on RN | |
| CN117369947B (en) | Management method and management system for container mirror image | |
| CN108733378A (en) | The method for supporting multiple primary Cocos game to be linked into Android application platform | |
| CN113797553B (en) | Subcontracting resource downloading method and device, storage medium and electronic equipment | |
| CN113347620B (en) | Method, device, equipment and storage medium for compatibility of multi-version application air card issuing |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |