File manager - Edit - /opt/saltstack/salt/lib/python3.10/site-packages/salt/states/__pycache__/docker_image.cpython-310.pyc
Back
o ;j}B � @ s� d Z ddlZddlZddlZddlmZ e�e�Z dZ dZ dd� Z dddddej jjddd d ddf d d �Zdd d�Zddd�ZdS )av Management of Docker images .. versionadded:: 2017.7.0 :depends: docker_ Python module .. note:: Older releases of the Python bindings for Docker were called docker-py_ in PyPI. All releases of docker_, and releases of docker-py_ >= 1.6.0 are supported. These python bindings can easily be installed using :py:func:`pip.install <salt.modules.pip.install>`: .. code-block:: bash salt myminion pip.install docker To upgrade from docker-py_ to docker_, you must first uninstall docker-py_, and then install docker_: .. code-block:: bash salt myminion pip.uninstall docker-py salt myminion pip.install docker .. _docker: https://pypi.python.org/pypi/docker .. _docker-py: https://pypi.python.org/pypi/docker-py These states were moved from the :mod:`docker <salt.states.docker>` state module (formerly called **dockerng**) in the 2017.7.0 release. .. note:: To pull from a Docker registry, authentication must be configured. See :ref:`here <docker-authentication>` for more information on how to configure access to docker registries in :ref:`Pillar <pillar>` data. � N)�CommandExecutionErrorZ docker_image)Z moby_imagec C s dt v rtS dt �d�fS )z? Only load if the docker execution module is available zdocker.versionF)�__salt__�__virtualname__Zmissing_fun_string� r r �L/opt/saltstack/salt/lib/python3.10/site-packages/salt/states/docker_image.py� __virtual__4 s r Fzopensuse/python�basec s | i ddd�}t | t�st| �} tdd� |||fD ��}|dkr&d|d< |S |dkrC|s2d |d< |S t |t�s;t|�}d �| |f�}n |rL| � d |� �} | }ztd |�}W n) ty } z t|�}d |v rid }n ||d< |W Y d }~S W Y d }~nd }~ww |d ur�|s�d|d< d|� d�|d< |S |s�|r�d}n|r�d}nd}td r�d |d< |d ur�|s�|d u r�d|� d|� �|d< |S |�r@tjj � td �}t t t |j |j���}|D ]}|| �di �v r�| �di ��|�||< q�z||d< | |d< ||d< ||d < td d6i |��}W n t�y( } zd �|||�|d< |W Y d }~S d }~ww |d u �s;|d |d d d � k�r?||d < n�|�r�t� � � fd!d"�d#D �}ztd$ d6| || |d%�|��}W n t�y} } zd&�|||�|d< |W Y d }~S d }~ww |d u �s�|d |d d d � k�r�||d < n�|�r�z td' || |d(�}W n t�y� } zd)�|||�|d< |W Y d }~S d }~ww |d u �s�|�d*g ��r�||d < nZz td+ | ||d,�}W n t�y� } zd-|� d.|� �|d< |W Y d }~S d }~ww |d u�r|d d d � |�d*i ��d/d g�d0 k�rn|d u �s)|�d*i ��d1��r-||d < d}ztd |� W n# t�yZ } zt|�}d |v�rPd2�|||�}W Y d }~nd }~ww |�rd||d< |S d|d< |d �swd3�| |�|d< |S d4|� d5|� �|d< |S )7a� .. versionchanged:: 2018.3.0 The ``tag`` argument has been added. It is now required unless pulling from a registry. Ensure that an image is present. The image can either be pulled from a Docker registry, built from a Dockerfile, loaded from a saved image, or built by running SLS files against a base image. If none of the ``build``, ``load``, or ``sls`` arguments are used, then Salt will pull from the :ref:`configured registries <docker-authentication>`. If the specified image already exists, it will not be pulled unless ``force`` is set to ``True``. Here is an example of a state that will pull an image from the Docker Hub: .. code-block:: yaml myuser/myimage: docker_image.present: - tag: mytag name The name of the docker image. tag Tag name for the image. Required when using ``build``, ``load``, or ``sls`` to create the image, but optional if pulling from a repository. .. versionadded:: 2018.3.0 build Path to directory on the Minion containing a Dockerfile .. code-block:: yaml myuser/myimage: docker_image.present: - build: /home/myuser/docker/myimage - tag: mytag myuser/myimage: docker_image.present: - build: /home/myuser/docker/myimage - tag: mytag - dockerfile: Dockerfile.alternative The image will be built using :py:func:`docker.build <salt.modules.dockermod.build>` and the specified image name and tag will be applied to it. .. versionadded:: 2016.11.0 .. versionchanged:: 2018.3.0 The ``tag`` must be manually specified using the ``tag`` argument. load Loads a tar archive created with :py:func:`docker.save <salt.modules.dockermod.save>` (or the ``docker save`` Docker CLI command), and assigns it the specified repo and tag. .. code-block:: yaml myuser/myimage: docker_image.present: - load: salt://path/to/image.tar - tag: mytag .. versionchanged:: 2018.3.0 The ``tag`` must be manually specified using the ``tag`` argument. force Set this parameter to ``True`` to force Salt to pull/build/load the image even if it is already present. insecure_registry If ``True``, the Docker client will permit the use of insecure (non-HTTPS) registries. client_timeout Timeout in seconds for the Docker client. This is not a timeout for the state, but for receiving a response from the API. dockerfile Allows for an alternative Dockerfile to be specified. Path to alternative Dockefile is relative to the build path for the Docker container. .. versionadded:: 2016.11.0 sls Allow for building of image with :py:func:`docker.sls_build <salt.modules.dockermod.sls_build>` by specifying the SLS files with which to build. This can be a list or comma-separated string. .. code-block:: yaml myuser/myimage: docker_image.present: - tag: latest - sls: - webapp1 - webapp2 - base: centos - saltenv: base .. versionadded:: 2017.7.0 .. versionchanged:: 2018.3.0 The ``tag`` must be manually specified using the ``tag`` argument. base Base image with which to start :py:func:`docker.sls_build <salt.modules.dockermod.sls_build>` .. versionadded:: 2017.7.0 saltenv Specify the environment from which to retrieve the SLS indicated by the `mods` parameter. .. versionadded:: 2017.7.0 .. versionchanged:: 2018.3.0 Now uses the effective saltenv if not explicitly passed. In earlier versions, ``base`` was assumed as a default. pillarenv Specify a Pillar environment to be used when applying states. This can also be set in the minion config file using the :conf_minion:`pillarenv` option. When neither the :conf_minion:`pillarenv` minion config option nor this CLI argument is used, all Pillar environments will be merged together. .. versionadded:: 2018.3.0 pillar Custom Pillar values, passed as a dictionary of key-value pairs .. note:: Values passed this way will override Pillar values set via ``pillar_roots`` or an external Pillar source. .. versionadded:: 2018.3.0 kwargs Additional keyword arguments to pass to :py:func:`docker.build <salt.modules.dockermod.build>` F� ��name�changes�result�commentc S s g | ]}|d ur|�qS �Nr ��.0�xr r r � <listcomp>� � zpresent.<locals>.<listcomp>� z3Only one of 'build', 'load', or 'sls' is permitted.r zOThe 'tag' argument is required if any one of 'build', 'load', or 'sls' is used.�:zdocker.inspect_imageZ404NTr �Image z already presentZbuiltZloadedZpulled�testz will be z docker.build�kwargs�path� repository�tag� dockerfilez'Encountered error building {} as {}: {}ZId� r c s" i | ] }� | d ur|� | �qS r r )r �k�Z_localsr r � <dictcomp>/ s �zpresent.<locals>.<dictcomp>)�saltenv� pillarenv�pillarzdocker.sls_build)r r r �modsz2Encountered error using SLS {} for building {}: {}z docker.load)r r r z&Encountered error loading {} as {}: {}ZLayersz docker.pull)�insecure_registry�client_timeoutzEncountered error pulling z: ZAlready_Pulledr ZPulledz0Failed to inspect image '{}' after it was {}: {}z,Image '{}' was {}, but there were no changeszImage 'z' was r )� isinstance�str�len�joinr r �__opts__�salt�utils�argsZget_function_argspec�dict�list�zip�defaults�get� Exception�format�locals)r r �build�load�forcer& r' r Zslsr r" r# r$ r �retZnum_build_argsZ full_imageZ image_info�exc�msg�actionZargspecZ build_argsr Z image_updateZsls_build_kwargs�errorr r r �present= s ! � ��� ����$� �� �����$����� ��� � ��� � ��r@ c s� | i ddd�}| s|sd|d< |S |dur|}n| r | g}g }|D ]}t d |�}|dur2|�|� q!|sOd|d < t|�d krId | � d �|d< |S d |d< |S td rud|d < t|�d krid |d � d�|d< |S d�d�|��|d< |S t d |d|i�}t d � � � fdd�|D �} | r�� fdd�|D �r�||d< d�d�| ��|d< |S d|d< d |v r�|d d �d �|d ��7 < |S ||d< t|�d kr�d |d � d �|d< n d �d�|��|d< d|d < |S )!aK Ensure that an image is absent from the Minion. Image names can be specified either using ``repo:tag`` notation, or just the repo name (in which case a tag of ``latest`` is assumed). name The name of the docker image. images Run this state on more than one image at a time. The following two examples accomplish the same thing: .. code-block:: yaml remove_images: docker_image.absent: - names: - busybox - centos:6 - nginx .. code-block:: yaml remove_images: docker_image.absent: - images: - busybox - centos:6 - nginx However, the second example will be a bit quicker since Salt will do all the deletions in a single run, rather than executing the state separately on each image (as it would in the first example). force Salt will fail to remove any images currently in use by a container. Set this option to true to remove the image even if it is already present. .. note:: This option can also be overridden by Pillar data. If the Minion has a pillar variable named ``docker.running.force`` which is set to ``True``, it will turn on this option. This pillar variable can even be set at runtime. For example: .. code-block:: bash salt myminion state.sls docker_stuff pillar="{docker.force: True}" If this pillar variable is present and set to ``False``, then it will turn off this option. For more granular control, setting a pillar variable named ``docker.force.image_name`` will affect only the named image. Fr r z+One of 'name' and 'images' must be providedr Nzdocker.resolve_tagTr r r z is not presentz$All specified images are not presentr r z will be removedz(The following images will be removed: {}z, z docker.rmir: zdocker.list_tagsc s g | ]}|� v r|�qS r r r �Z post_tagsr r r � r zabsent.<locals>.<listcomp>c s g | ]}|� vr|�qS r r r rA r r r � r r z/The following image(s) failed to be removed: {}z)None of the specified images were removedZErrorsz+. The following errors were encountered: {}z; z was removedz%The following images were removed: {})r �appendr* r, r6 r+ ) r Zimagesr: r; �targetsZ to_delete�targetZ resolved_tagr Zfailedr rA r �absenty sl 9 � � �� �� � � �rE c K s4 |dkrd|d< t | fi |��S | i dd|� �d�S )a9 The docker_image watcher, called to invoke the watch command. .. note:: This state exists to support special handling of the ``watch`` :ref:`requisite <requisites>`. It should not be called directly. Parameters for this function should be set by the state being triggered. r@ Tr: Fz'watch requisite is not implemented for r )r@ )r Zsfunr r r r � mod_watch� s �rF )NNFr )�__doc__�loggingZsalt.utils.argsr- Zsalt.utils.dockermodZsalt.exceptionsr � getLogger�__name__�logr Z__virtual_aliases__r r. Z dockermodZCLIENT_TIMEOUTr@ rE rF r r r r �<module> s4 % � >x
| ver. 1.4 |
Github
|
.
| PHP 8.2.30 | Generation time: 0 |
proxy
|
phpinfo
|
Settings