├── .github ├── ansible-test-tests │ └── ansible_collections │ │ └── testns │ │ └── testcol │ │ ├── galaxy.yml │ │ └── tests │ │ ├── .gitignore │ │ └── integration │ │ └── targets │ │ └── basic │ │ ├── aliases │ │ └── tasks │ │ └── main.yml ├── dependabot.yml └── workflows │ ├── ansible-test.yml │ ├── eerelease.yml │ └── execution-environments.yml ├── .gitignore ├── LICENSE ├── README.md ├── ansible-test ├── README.md ├── archlinux │ ├── build.sh │ ├── dependencies.txt │ └── requirements.txt ├── debian-bookworm │ ├── build.sh │ ├── dependencies.txt │ └── requirements.txt └── debian-bullseye │ ├── build.sh │ ├── dependencies.txt │ └── requirements.txt ├── docs └── community-ee │ ├── community-ee-announcement.md │ └── community-ee-release-process.md └── execution-environments ├── README.md ├── community-ee-base ├── execution-environment.yml └── tests.yml └── community-ee-minimal ├── execution-environment.yml └── tests.yml /.github/ansible-test-tests/ansible_collections/testns/testcol/galaxy.yml: -------------------------------------------------------------------------------- 1 | --- 2 | namespace: testns 3 | name: testcol 4 | version: 0.0.1 5 | -------------------------------------------------------------------------------- /.github/ansible-test-tests/ansible_collections/testns/testcol/tests/.gitignore: -------------------------------------------------------------------------------- 1 | /output/ 2 | -------------------------------------------------------------------------------- /.github/ansible-test-tests/ansible_collections/testns/testcol/tests/integration/targets/basic/aliases: -------------------------------------------------------------------------------- 1 | shippable/posix/group1 2 | -------------------------------------------------------------------------------- /.github/ansible-test-tests/ansible_collections/testns/testcol/tests/integration/targets/basic/tasks/main.yml: -------------------------------------------------------------------------------- 1 | --- 2 | - name: Test 3 | ping: 4 | -------------------------------------------------------------------------------- /.github/dependabot.yml: -------------------------------------------------------------------------------- 1 | --- 2 | # Copyright (c) Ansible Project 3 | # GNU General Public License v3.0+ (see LICENSES/GPL-3.0-or-later.txt or https://www.gnu.org/licenses/gpl-3.0.txt) 4 | # SPDX-License-Identifier: GPL-3.0-or-later 5 | 6 | version: 2 7 | updates: 8 | - package-ecosystem: "github-actions" 9 | directory: "/" 10 | schedule: 11 | interval: "weekly" 12 | -------------------------------------------------------------------------------- /.github/workflows/ansible-test.yml: -------------------------------------------------------------------------------- 1 | --- 2 | name: ansible-test images 3 | 4 | on: 5 | push: 6 | branches: 7 | - main 8 | paths: 9 | - .github/workflows/ansible-test.yml 10 | - ansible-test/** 11 | pull_request: 12 | branches: 13 | - main 14 | paths: 15 | - .github/workflows/ansible-test.yml 16 | - ansible-test/** 17 | workflow_dispatch: 18 | # Run daily (Monday at 08:00 UTC) 19 | schedule: 20 | - cron: '0 8 * * *' 21 | 22 | env: 23 | CONTAINER_REGISTRY: quay.io 24 | CONTAINER_IMAGE_NAME: ansible-community/test-image 25 | 26 | jobs: 27 | build: 28 | name: 'Build ansible-test images (${{ matrix.name }} with Python ${{ matrix.python }})' 29 | runs-on: ubuntu-24.04 30 | strategy: 31 | fail-fast: false 32 | matrix: 33 | include: 34 | - name: archlinux 35 | python: '3.13' 36 | ansible-core-1: ansible-core 37 | ansible-core-2: devel 38 | test-with-podman: true 39 | test-with-docker: true 40 | - name: debian-bullseye 41 | python: '3.9' 42 | ansible-core-1: ansible-core 43 | ansible-core-2: devel 44 | test-with-podman: true 45 | test-with-docker: true 46 | - name: debian-bookworm 47 | python: '3.11' 48 | ansible-core-1: ansible-core 49 | ansible-core-2: devel 50 | test-with-podman: true 51 | test-with-docker: true 52 | 53 | steps: 54 | - name: Check out repository 55 | uses: actions/checkout@v4 56 | with: 57 | persist-credentials: false 58 | 59 | - name: Set up Python 3.13 60 | uses: actions/setup-python@v5 61 | with: 62 | python-version: "3.13" 63 | 64 | - name: Install dependencies 65 | env: 66 | ANSIBLE_CORE_1: ${{ matrix.ansible-core-1 }} 67 | run: | 68 | sudo apt-get install podman buildah 69 | pip install "${ANSIBLE_CORE_1}" 70 | 71 | - name: Build ${{ matrix.name }} image 72 | env: 73 | NAME: ${{ matrix.name }} 74 | run: | 75 | "${NAME}/build.sh" 76 | podman tag "localhost/test-image:${NAME}" "${CONTAINER_REGISTRY}/${CONTAINER_IMAGE_NAME}:${NAME}" 77 | working-directory: ./ansible-test/ 78 | 79 | # This is necessary to allow running systemd in rootless containers 80 | - name: Start systemd user service 81 | run: | 82 | loginctl enable-linger runner 83 | sleep 1 84 | 85 | - name: Run basic tests with ${{ matrix.name }} image (${{ matrix.ansible-core-1 }}, Python versions ${{ matrix.python }}, Podman) 86 | if: ${{ matrix.test-with-podman }} 87 | env: 88 | NAME: ${{ matrix.name }} 89 | PYTHON_VERSIONS: ${{ matrix.python }} 90 | ANSIBLE_TEST_PREFER_PODMAN: 1 91 | run: | 92 | for PYTHON in ${PYTHON_VERSIONS}; do 93 | ansible-test integration --color -v --python "${PYTHON}" --docker "localhost/test-image:${NAME}" shippable/posix/group1/ 94 | done 95 | working-directory: ./.github/ansible-test-tests/ansible_collections/testns/testcol 96 | 97 | - name: Copy image from podman to docker 98 | if: ${{ matrix.test-with-docker }} 99 | env: 100 | NAME: ${{ matrix.name }} 101 | run: | 102 | podman push "localhost/test-image:${NAME}" "docker-daemon:localhost/test-image:${NAME}" 103 | 104 | - name: Install ansible-core ${{ matrix.ansible-core-2 }} 105 | if: ${{ matrix.test-with-docker }} 106 | env: 107 | ANSIBLE_CORE_2: ${{ matrix.ansible-core-2 }} 108 | run: | 109 | pip install "https://github.com/ansible/ansible/archive/${ANSIBLE_CORE_2}.tar.gz" 110 | 111 | - name: Run basic tests with ${{ matrix.name }} image (ansible-core ${{ matrix.ansible-core-2 }}, Python versions ${{ matrix.python }}, Docker) 112 | if: ${{ matrix.test-with-docker }} 113 | env: 114 | NAME: ${{ matrix.name }} 115 | PYTHON_VERSIONS: ${{ matrix.python }} 116 | run: | 117 | for PYTHON in ${PYTHON_VERSIONS}; do 118 | ansible-test integration --color -v --python "${PYTHON}" --docker "localhost/test-image:${NAME}" shippable/posix/group1/ 119 | done 120 | working-directory: ./.github/ansible-test-tests/ansible_collections/testns/testcol 121 | 122 | - name: Publish container image as ${{ env.CONTAINER_REGISTRY }}/${{ env.CONTAINER_IMAGE_NAME }}:${{ matrix.name }} 123 | if: github.event_name != 'pull_request' 124 | uses: redhat-actions/push-to-registry@v2 125 | with: 126 | registry: ${{ env.CONTAINER_REGISTRY }} 127 | image: ${{ env.CONTAINER_IMAGE_NAME }} 128 | tags: ${{ matrix.name }} 129 | username: ${{ secrets.quay_write_user }} 130 | password: ${{ secrets.quay_write_pass }} 131 | -------------------------------------------------------------------------------- /.github/workflows/eerelease.yml: -------------------------------------------------------------------------------- 1 | name: Release Ansible Execution Environment 2 | on: 3 | workflow_dispatch: 4 | inputs: 5 | ee-name: 6 | description: 'EE name' 7 | required: true 8 | type: choice 9 | options: 10 | - community-ee-base 11 | - community-ee-minimal 12 | ansible-core-version: 13 | description: >- 14 | Ansible-core version. Example: 2.17.0 15 | required: true 16 | ee-version: 17 | description: >- 18 | EE Release Version, to be appended to the ansible-core version. Example: 1 19 | required: true 20 | tag_as_latest: 21 | description: >- 22 | Whether to tag the image as latest. 23 | type: boolean 24 | required: false 25 | default: false 26 | 27 | env: 28 | EE_VERSION: ${{ inputs.ansible-core-version }}-${{ inputs.ee-version }} 29 | IMAGE_NAME: ${{ github.repository_owner }}/${{ inputs.ee-name }} 30 | 31 | jobs: 32 | build: 33 | name: Build Execution Environment ${{ inputs.ansible-core-version }}-${{ inputs.ee-version }} 34 | runs-on: ubuntu-latest 35 | permissions: 36 | pull-requests: write 37 | contents: write 38 | packages: write 39 | 40 | steps: 41 | - name: Check out images 42 | uses: actions/checkout@v4 43 | with: 44 | repository: ansible-community/images 45 | ref: main 46 | path: image 47 | persist-credentials: false 48 | 49 | - name: Check out eercheck repo for testing 50 | uses: actions/checkout@v4 51 | with: 52 | repository: anweshadas/eercheck 53 | ref: main 54 | path: eercheck 55 | persist-credentials: false 56 | 57 | - name: Set up Python 3.11 58 | uses: actions/setup-python@v5 59 | with: 60 | python-version: 3.11 61 | 62 | - name: Install dependencies 63 | run: | 64 | python3 -m pip install ansible-builder 65 | python3 -m pip install setuptools 66 | sudo apt install podman --yes 67 | pwd 68 | ls -l 69 | 70 | - name: Pull the latest fedora image 71 | run: | 72 | podman pull quay.io/fedora/fedora:latest 73 | 74 | - name: Build Community EE image 75 | working-directory: image/execution-environments/${{ inputs.ee-name }} 76 | run: | 77 | ansible-builder build --tag "ghcr.io/${IMAGE_NAME}:${EE_VERSION}" 78 | 79 | - name: Find the id of the latest EE image 80 | run: | 81 | echo "IMAGE_ID=$(podman images -q "${IMAGE_NAME}:${EE_VERSION}")">>$GITHUB_ENV 82 | 83 | - name: Test the image with eercheck 84 | working-directory: eercheck 85 | run: | 86 | pwd 87 | ls -l 88 | python3 -m venv .venv 89 | source .venv/bin/activate 90 | python -m pip install -r requirements.txt 91 | sudo systemctl start podman.socket 92 | ./containertest.py "${IMAGE_ID}" 93 | 94 | - name: Create the latest tag 95 | if: ${{ inputs.tag_as_latest }} 96 | run: | 97 | podman tag "${IMAGE_ID}" "ghcr.io/${IMAGE_NAME}:latest" 98 | podman images 99 | 100 | - name: Upload artifact EE to ghcr 101 | uses: redhat-actions/push-to-registry@v2 102 | with: 103 | image: ${{ inputs.ee-name }} 104 | tags: >- 105 | ${{ env.EE_VERSION }} 106 | ${{ 107 | inputs.tag_as_latest 108 | && 'latest' 109 | || '' 110 | }} 111 | registry: ghcr.io/${{ github.repository_owner }} 112 | username: ${{ github.actor }} 113 | password: ${{ secrets.GITHUB_TOKEN }} 114 | -------------------------------------------------------------------------------- /.github/workflows/execution-environments.yml: -------------------------------------------------------------------------------- 1 | name: execution environment images 2 | 3 | on: 4 | push: 5 | branches: 6 | - main 7 | paths: 8 | - .github/workflows/execution-environments.yml 9 | - execution-environments/** 10 | pull_request: 11 | branches: 12 | - main 13 | paths: 14 | - .github/workflows/execution-environments.yml 15 | - execution-environments/** 16 | workflow_dispatch: 17 | # Run once per week (Monday at 08:00 UTC) 18 | schedule: 19 | - cron: '0 8 * * 1' 20 | 21 | jobs: 22 | build: 23 | name: 'Build EE image: ${{ matrix.name }}' 24 | runs-on: ubuntu-latest 25 | strategy: 26 | fail-fast: false 27 | matrix: 28 | include: 29 | - name: community-ee-base 30 | - name: community-ee-minimal 31 | 32 | steps: 33 | - name: Check out repository 34 | uses: actions/checkout@v4 35 | with: 36 | persist-credentials: false 37 | 38 | - name: Set up Python 3.13 39 | uses: actions/setup-python@v5 40 | with: 41 | python-version: "3.13" 42 | 43 | - name: Install dependencies 44 | run: | 45 | sudo apt-get install podman 46 | pip install ansible-core ansible-builder ansible-navigator 47 | 48 | - name: Build ${{ matrix.name }} image 49 | env: 50 | NAME: ${{ matrix.name }} 51 | run: | 52 | ansible-builder build -v 3 -t "test-ee:${NAME}" 53 | working-directory: ./execution-environments/${{ matrix.name }} 54 | 55 | - name: Run basic tests with ${{ matrix.name }} image 56 | env: 57 | NAME: ${{ matrix.name }} 58 | run: | 59 | ansible-navigator -v --mode stdout --pull-policy never \ 60 | --execution-environment-image "test-ee:${NAME}" \ 61 | run tests.yml 62 | working-directory: ./execution-environments/${{ matrix.name }} 63 | -------------------------------------------------------------------------------- /.gitignore: -------------------------------------------------------------------------------- 1 | execution-environments/*/context 2 | execution-environments/*/ansible-navigator.log 3 | execution-environments/*/*artifact*.json 4 | /.idea/ 5 | -------------------------------------------------------------------------------- /LICENSE: -------------------------------------------------------------------------------- 1 | GNU GENERAL PUBLIC LICENSE 2 | Version 3, 29 June 2007 3 | 4 | Copyright (C) 2007 Free Software Foundation, Inc. 5 | Everyone is permitted to copy and distribute verbatim copies 6 | of this license document, but changing it is not allowed. 7 | 8 | Preamble 9 | 10 | The GNU General Public License is a free, copyleft license for 11 | software and other kinds of works. 12 | 13 | The licenses for most software and other practical works are designed 14 | to take away your freedom to share and change the works. By contrast, 15 | the GNU General Public License is intended to guarantee your freedom to 16 | share and change all versions of a program--to make sure it remains free 17 | software for all its users. We, the Free Software Foundation, use the 18 | GNU General Public License for most of our software; it applies also to 19 | any other work released this way by its authors. You can apply it to 20 | your programs, too. 21 | 22 | When we speak of free software, we are referring to freedom, not 23 | price. Our General Public Licenses are designed to make sure that you 24 | have the freedom to distribute copies of free software (and charge for 25 | them if you wish), that you receive source code or can get it if you 26 | want it, that you can change the software or use pieces of it in new 27 | free programs, and that you know you can do these things. 28 | 29 | To protect your rights, we need to prevent others from denying you 30 | these rights or asking you to surrender the rights. Therefore, you have 31 | certain responsibilities if you distribute copies of the software, or if 32 | you modify it: responsibilities to respect the freedom of others. 33 | 34 | For example, if you distribute copies of such a program, whether 35 | gratis or for a fee, you must pass on to the recipients the same 36 | freedoms that you received. You must make sure that they, too, receive 37 | or can get the source code. And you must show them these terms so they 38 | know their rights. 39 | 40 | Developers that use the GNU GPL protect your rights with two steps: 41 | (1) assert copyright on the software, and (2) offer you this License 42 | giving you legal permission to copy, distribute and/or modify it. 43 | 44 | For the developers' and authors' protection, the GPL clearly explains 45 | that there is no warranty for this free software. For both users' and 46 | authors' sake, the GPL requires that modified versions be marked as 47 | changed, so that their problems will not be attributed erroneously to 48 | authors of previous versions. 49 | 50 | Some devices are designed to deny users access to install or run 51 | modified versions of the software inside them, although the manufacturer 52 | can do so. This is fundamentally incompatible with the aim of 53 | protecting users' freedom to change the software. The systematic 54 | pattern of such abuse occurs in the area of products for individuals to 55 | use, which is precisely where it is most unacceptable. Therefore, we 56 | have designed this version of the GPL to prohibit the practice for those 57 | products. If such problems arise substantially in other domains, we 58 | stand ready to extend this provision to those domains in future versions 59 | of the GPL, as needed to protect the freedom of users. 60 | 61 | Finally, every program is threatened constantly by software patents. 62 | States should not allow patents to restrict development and use of 63 | software on general-purpose computers, but in those that do, we wish to 64 | avoid the special danger that patents applied to a free program could 65 | make it effectively proprietary. To prevent this, the GPL assures that 66 | patents cannot be used to render the program non-free. 67 | 68 | The precise terms and conditions for copying, distribution and 69 | modification follow. 70 | 71 | TERMS AND CONDITIONS 72 | 73 | 0. Definitions. 74 | 75 | "This License" refers to version 3 of the GNU General Public License. 76 | 77 | "Copyright" also means copyright-like laws that apply to other kinds of 78 | works, such as semiconductor masks. 79 | 80 | "The Program" refers to any copyrightable work licensed under this 81 | License. Each licensee is addressed as "you". "Licensees" and 82 | "recipients" may be individuals or organizations. 83 | 84 | To "modify" a work means to copy from or adapt all or part of the work 85 | in a fashion requiring copyright permission, other than the making of an 86 | exact copy. The resulting work is called a "modified version" of the 87 | earlier work or a work "based on" the earlier work. 88 | 89 | A "covered work" means either the unmodified Program or a work based 90 | on the Program. 91 | 92 | To "propagate" a work means to do anything with it that, without 93 | permission, would make you directly or secondarily liable for 94 | infringement under applicable copyright law, except executing it on a 95 | computer or modifying a private copy. Propagation includes copying, 96 | distribution (with or without modification), making available to the 97 | public, and in some countries other activities as well. 98 | 99 | To "convey" a work means any kind of propagation that enables other 100 | parties to make or receive copies. Mere interaction with a user through 101 | a computer network, with no transfer of a copy, is not conveying. 102 | 103 | An interactive user interface displays "Appropriate Legal Notices" 104 | to the extent that it includes a convenient and prominently visible 105 | feature that (1) displays an appropriate copyright notice, and (2) 106 | tells the user that there is no warranty for the work (except to the 107 | extent that warranties are provided), that licensees may convey the 108 | work under this License, and how to view a copy of this License. If 109 | the interface presents a list of user commands or options, such as a 110 | menu, a prominent item in the list meets this criterion. 111 | 112 | 1. Source Code. 113 | 114 | The "source code" for a work means the preferred form of the work 115 | for making modifications to it. "Object code" means any non-source 116 | form of a work. 117 | 118 | A "Standard Interface" means an interface that either is an official 119 | standard defined by a recognized standards body, or, in the case of 120 | interfaces specified for a particular programming language, one that 121 | is widely used among developers working in that language. 122 | 123 | The "System Libraries" of an executable work include anything, other 124 | than the work as a whole, that (a) is included in the normal form of 125 | packaging a Major Component, but which is not part of that Major 126 | Component, and (b) serves only to enable use of the work with that 127 | Major Component, or to implement a Standard Interface for which an 128 | implementation is available to the public in source code form. A 129 | "Major Component", in this context, means a major essential component 130 | (kernel, window system, and so on) of the specific operating system 131 | (if any) on which the executable work runs, or a compiler used to 132 | produce the work, or an object code interpreter used to run it. 133 | 134 | The "Corresponding Source" for a work in object code form means all 135 | the source code needed to generate, install, and (for an executable 136 | work) run the object code and to modify the work, including scripts to 137 | control those activities. However, it does not include the work's 138 | System Libraries, or general-purpose tools or generally available free 139 | programs which are used unmodified in performing those activities but 140 | which are not part of the work. For example, Corresponding Source 141 | includes interface definition files associated with source files for 142 | the work, and the source code for shared libraries and dynamically 143 | linked subprograms that the work is specifically designed to require, 144 | such as by intimate data communication or control flow between those 145 | subprograms and other parts of the work. 146 | 147 | The Corresponding Source need not include anything that users 148 | can regenerate automatically from other parts of the Corresponding 149 | Source. 150 | 151 | The Corresponding Source for a work in source code form is that 152 | same work. 153 | 154 | 2. Basic Permissions. 155 | 156 | All rights granted under this License are granted for the term of 157 | copyright on the Program, and are irrevocable provided the stated 158 | conditions are met. This License explicitly affirms your unlimited 159 | permission to run the unmodified Program. The output from running a 160 | covered work is covered by this License only if the output, given its 161 | content, constitutes a covered work. This License acknowledges your 162 | rights of fair use or other equivalent, as provided by copyright law. 163 | 164 | You may make, run and propagate covered works that you do not 165 | convey, without conditions so long as your license otherwise remains 166 | in force. You may convey covered works to others for the sole purpose 167 | of having them make modifications exclusively for you, or provide you 168 | with facilities for running those works, provided that you comply with 169 | the terms of this License in conveying all material for which you do 170 | not control copyright. Those thus making or running the covered works 171 | for you must do so exclusively on your behalf, under your direction 172 | and control, on terms that prohibit them from making any copies of 173 | your copyrighted material outside their relationship with you. 174 | 175 | Conveying under any other circumstances is permitted solely under 176 | the conditions stated below. Sublicensing is not allowed; section 10 177 | makes it unnecessary. 178 | 179 | 3. Protecting Users' Legal Rights From Anti-Circumvention Law. 180 | 181 | No covered work shall be deemed part of an effective technological 182 | measure under any applicable law fulfilling obligations under article 183 | 11 of the WIPO copyright treaty adopted on 20 December 1996, or 184 | similar laws prohibiting or restricting circumvention of such 185 | measures. 186 | 187 | When you convey a covered work, you waive any legal power to forbid 188 | circumvention of technological measures to the extent such circumvention 189 | is effected by exercising rights under this License with respect to 190 | the covered work, and you disclaim any intention to limit operation or 191 | modification of the work as a means of enforcing, against the work's 192 | users, your or third parties' legal rights to forbid circumvention of 193 | technological measures. 194 | 195 | 4. Conveying Verbatim Copies. 196 | 197 | You may convey verbatim copies of the Program's source code as you 198 | receive it, in any medium, provided that you conspicuously and 199 | appropriately publish on each copy an appropriate copyright notice; 200 | keep intact all notices stating that this License and any 201 | non-permissive terms added in accord with section 7 apply to the code; 202 | keep intact all notices of the absence of any warranty; and give all 203 | recipients a copy of this License along with the Program. 204 | 205 | You may charge any price or no price for each copy that you convey, 206 | and you may offer support or warranty protection for a fee. 207 | 208 | 5. Conveying Modified Source Versions. 209 | 210 | You may convey a work based on the Program, or the modifications to 211 | produce it from the Program, in the form of source code under the 212 | terms of section 4, provided that you also meet all of these conditions: 213 | 214 | a) The work must carry prominent notices stating that you modified 215 | it, and giving a relevant date. 216 | 217 | b) The work must carry prominent notices stating that it is 218 | released under this License and any conditions added under section 219 | 7. This requirement modifies the requirement in section 4 to 220 | "keep intact all notices". 221 | 222 | c) You must license the entire work, as a whole, under this 223 | License to anyone who comes into possession of a copy. This 224 | License will therefore apply, along with any applicable section 7 225 | additional terms, to the whole of the work, and all its parts, 226 | regardless of how they are packaged. This License gives no 227 | permission to license the work in any other way, but it does not 228 | invalidate such permission if you have separately received it. 229 | 230 | d) If the work has interactive user interfaces, each must display 231 | Appropriate Legal Notices; however, if the Program has interactive 232 | interfaces that do not display Appropriate Legal Notices, your 233 | work need not make them do so. 234 | 235 | A compilation of a covered work with other separate and independent 236 | works, which are not by their nature extensions of the covered work, 237 | and which are not combined with it such as to form a larger program, 238 | in or on a volume of a storage or distribution medium, is called an 239 | "aggregate" if the compilation and its resulting copyright are not 240 | used to limit the access or legal rights of the compilation's users 241 | beyond what the individual works permit. Inclusion of a covered work 242 | in an aggregate does not cause this License to apply to the other 243 | parts of the aggregate. 244 | 245 | 6. Conveying Non-Source Forms. 246 | 247 | You may convey a covered work in object code form under the terms 248 | of sections 4 and 5, provided that you also convey the 249 | machine-readable Corresponding Source under the terms of this License, 250 | in one of these ways: 251 | 252 | a) Convey the object code in, or embodied in, a physical product 253 | (including a physical distribution medium), accompanied by the 254 | Corresponding Source fixed on a durable physical medium 255 | customarily used for software interchange. 256 | 257 | b) Convey the object code in, or embodied in, a physical product 258 | (including a physical distribution medium), accompanied by a 259 | written offer, valid for at least three years and valid for as 260 | long as you offer spare parts or customer support for that product 261 | model, to give anyone who possesses the object code either (1) a 262 | copy of the Corresponding Source for all the software in the 263 | product that is covered by this License, on a durable physical 264 | medium customarily used for software interchange, for a price no 265 | more than your reasonable cost of physically performing this 266 | conveying of source, or (2) access to copy the 267 | Corresponding Source from a network server at no charge. 268 | 269 | c) Convey individual copies of the object code with a copy of the 270 | written offer to provide the Corresponding Source. This 271 | alternative is allowed only occasionally and noncommercially, and 272 | only if you received the object code with such an offer, in accord 273 | with subsection 6b. 274 | 275 | d) Convey the object code by offering access from a designated 276 | place (gratis or for a charge), and offer equivalent access to the 277 | Corresponding Source in the same way through the same place at no 278 | further charge. You need not require recipients to copy the 279 | Corresponding Source along with the object code. If the place to 280 | copy the object code is a network server, the Corresponding Source 281 | may be on a different server (operated by you or a third party) 282 | that supports equivalent copying facilities, provided you maintain 283 | clear directions next to the object code saying where to find the 284 | Corresponding Source. Regardless of what server hosts the 285 | Corresponding Source, you remain obligated to ensure that it is 286 | available for as long as needed to satisfy these requirements. 287 | 288 | e) Convey the object code using peer-to-peer transmission, provided 289 | you inform other peers where the object code and Corresponding 290 | Source of the work are being offered to the general public at no 291 | charge under subsection 6d. 292 | 293 | A separable portion of the object code, whose source code is excluded 294 | from the Corresponding Source as a System Library, need not be 295 | included in conveying the object code work. 296 | 297 | A "User Product" is either (1) a "consumer product", which means any 298 | tangible personal property which is normally used for personal, family, 299 | or household purposes, or (2) anything designed or sold for incorporation 300 | into a dwelling. In determining whether a product is a consumer product, 301 | doubtful cases shall be resolved in favor of coverage. For a particular 302 | product received by a particular user, "normally used" refers to a 303 | typical or common use of that class of product, regardless of the status 304 | of the particular user or of the way in which the particular user 305 | actually uses, or expects or is expected to use, the product. A product 306 | is a consumer product regardless of whether the product has substantial 307 | commercial, industrial or non-consumer uses, unless such uses represent 308 | the only significant mode of use of the product. 309 | 310 | "Installation Information" for a User Product means any methods, 311 | procedures, authorization keys, or other information required to install 312 | and execute modified versions of a covered work in that User Product from 313 | a modified version of its Corresponding Source. The information must 314 | suffice to ensure that the continued functioning of the modified object 315 | code is in no case prevented or interfered with solely because 316 | modification has been made. 317 | 318 | If you convey an object code work under this section in, or with, or 319 | specifically for use in, a User Product, and the conveying occurs as 320 | part of a transaction in which the right of possession and use of the 321 | User Product is transferred to the recipient in perpetuity or for a 322 | fixed term (regardless of how the transaction is characterized), the 323 | Corresponding Source conveyed under this section must be accompanied 324 | by the Installation Information. But this requirement does not apply 325 | if neither you nor any third party retains the ability to install 326 | modified object code on the User Product (for example, the work has 327 | been installed in ROM). 328 | 329 | The requirement to provide Installation Information does not include a 330 | requirement to continue to provide support service, warranty, or updates 331 | for a work that has been modified or installed by the recipient, or for 332 | the User Product in which it has been modified or installed. Access to a 333 | network may be denied when the modification itself materially and 334 | adversely affects the operation of the network or violates the rules and 335 | protocols for communication across the network. 336 | 337 | Corresponding Source conveyed, and Installation Information provided, 338 | in accord with this section must be in a format that is publicly 339 | documented (and with an implementation available to the public in 340 | source code form), and must require no special password or key for 341 | unpacking, reading or copying. 342 | 343 | 7. Additional Terms. 344 | 345 | "Additional permissions" are terms that supplement the terms of this 346 | License by making exceptions from one or more of its conditions. 347 | Additional permissions that are applicable to the entire Program shall 348 | be treated as though they were included in this License, to the extent 349 | that they are valid under applicable law. If additional permissions 350 | apply only to part of the Program, that part may be used separately 351 | under those permissions, but the entire Program remains governed by 352 | this License without regard to the additional permissions. 353 | 354 | When you convey a copy of a covered work, you may at your option 355 | remove any additional permissions from that copy, or from any part of 356 | it. (Additional permissions may be written to require their own 357 | removal in certain cases when you modify the work.) You may place 358 | additional permissions on material, added by you to a covered work, 359 | for which you have or can give appropriate copyright permission. 360 | 361 | Notwithstanding any other provision of this License, for material you 362 | add to a covered work, you may (if authorized by the copyright holders of 363 | that material) supplement the terms of this License with terms: 364 | 365 | a) Disclaiming warranty or limiting liability differently from the 366 | terms of sections 15 and 16 of this License; or 367 | 368 | b) Requiring preservation of specified reasonable legal notices or 369 | author attributions in that material or in the Appropriate Legal 370 | Notices displayed by works containing it; or 371 | 372 | c) Prohibiting misrepresentation of the origin of that material, or 373 | requiring that modified versions of such material be marked in 374 | reasonable ways as different from the original version; or 375 | 376 | d) Limiting the use for publicity purposes of names of licensors or 377 | authors of the material; or 378 | 379 | e) Declining to grant rights under trademark law for use of some 380 | trade names, trademarks, or service marks; or 381 | 382 | f) Requiring indemnification of licensors and authors of that 383 | material by anyone who conveys the material (or modified versions of 384 | it) with contractual assumptions of liability to the recipient, for 385 | any liability that these contractual assumptions directly impose on 386 | those licensors and authors. 387 | 388 | All other non-permissive additional terms are considered "further 389 | restrictions" within the meaning of section 10. If the Program as you 390 | received it, or any part of it, contains a notice stating that it is 391 | governed by this License along with a term that is a further 392 | restriction, you may remove that term. If a license document contains 393 | a further restriction but permits relicensing or conveying under this 394 | License, you may add to a covered work material governed by the terms 395 | of that license document, provided that the further restriction does 396 | not survive such relicensing or conveying. 397 | 398 | If you add terms to a covered work in accord with this section, you 399 | must place, in the relevant source files, a statement of the 400 | additional terms that apply to those files, or a notice indicating 401 | where to find the applicable terms. 402 | 403 | Additional terms, permissive or non-permissive, may be stated in the 404 | form of a separately written license, or stated as exceptions; 405 | the above requirements apply either way. 406 | 407 | 8. Termination. 408 | 409 | You may not propagate or modify a covered work except as expressly 410 | provided under this License. Any attempt otherwise to propagate or 411 | modify it is void, and will automatically terminate your rights under 412 | this License (including any patent licenses granted under the third 413 | paragraph of section 11). 414 | 415 | However, if you cease all violation of this License, then your 416 | license from a particular copyright holder is reinstated (a) 417 | provisionally, unless and until the copyright holder explicitly and 418 | finally terminates your license, and (b) permanently, if the copyright 419 | holder fails to notify you of the violation by some reasonable means 420 | prior to 60 days after the cessation. 421 | 422 | Moreover, your license from a particular copyright holder is 423 | reinstated permanently if the copyright holder notifies you of the 424 | violation by some reasonable means, this is the first time you have 425 | received notice of violation of this License (for any work) from that 426 | copyright holder, and you cure the violation prior to 30 days after 427 | your receipt of the notice. 428 | 429 | Termination of your rights under this section does not terminate the 430 | licenses of parties who have received copies or rights from you under 431 | this License. If your rights have been terminated and not permanently 432 | reinstated, you do not qualify to receive new licenses for the same 433 | material under section 10. 434 | 435 | 9. Acceptance Not Required for Having Copies. 436 | 437 | You are not required to accept this License in order to receive or 438 | run a copy of the Program. Ancillary propagation of a covered work 439 | occurring solely as a consequence of using peer-to-peer transmission 440 | to receive a copy likewise does not require acceptance. However, 441 | nothing other than this License grants you permission to propagate or 442 | modify any covered work. These actions infringe copyright if you do 443 | not accept this License. Therefore, by modifying or propagating a 444 | covered work, you indicate your acceptance of this License to do so. 445 | 446 | 10. Automatic Licensing of Downstream Recipients. 447 | 448 | Each time you convey a covered work, the recipient automatically 449 | receives a license from the original licensors, to run, modify and 450 | propagate that work, subject to this License. You are not responsible 451 | for enforcing compliance by third parties with this License. 452 | 453 | An "entity transaction" is a transaction transferring control of an 454 | organization, or substantially all assets of one, or subdividing an 455 | organization, or merging organizations. If propagation of a covered 456 | work results from an entity transaction, each party to that 457 | transaction who receives a copy of the work also receives whatever 458 | licenses to the work the party's predecessor in interest had or could 459 | give under the previous paragraph, plus a right to possession of the 460 | Corresponding Source of the work from the predecessor in interest, if 461 | the predecessor has it or can get it with reasonable efforts. 462 | 463 | You may not impose any further restrictions on the exercise of the 464 | rights granted or affirmed under this License. For example, you may 465 | not impose a license fee, royalty, or other charge for exercise of 466 | rights granted under this License, and you may not initiate litigation 467 | (including a cross-claim or counterclaim in a lawsuit) alleging that 468 | any patent claim is infringed by making, using, selling, offering for 469 | sale, or importing the Program or any portion of it. 470 | 471 | 11. Patents. 472 | 473 | A "contributor" is a copyright holder who authorizes use under this 474 | License of the Program or a work on which the Program is based. The 475 | work thus licensed is called the contributor's "contributor version". 476 | 477 | A contributor's "essential patent claims" are all patent claims 478 | owned or controlled by the contributor, whether already acquired or 479 | hereafter acquired, that would be infringed by some manner, permitted 480 | by this License, of making, using, or selling its contributor version, 481 | but do not include claims that would be infringed only as a 482 | consequence of further modification of the contributor version. For 483 | purposes of this definition, "control" includes the right to grant 484 | patent sublicenses in a manner consistent with the requirements of 485 | this License. 486 | 487 | Each contributor grants you a non-exclusive, worldwide, royalty-free 488 | patent license under the contributor's essential patent claims, to 489 | make, use, sell, offer for sale, import and otherwise run, modify and 490 | propagate the contents of its contributor version. 491 | 492 | In the following three paragraphs, a "patent license" is any express 493 | agreement or commitment, however denominated, not to enforce a patent 494 | (such as an express permission to practice a patent or covenant not to 495 | sue for patent infringement). To "grant" such a patent license to a 496 | party means to make such an agreement or commitment not to enforce a 497 | patent against the party. 498 | 499 | If you convey a covered work, knowingly relying on a patent license, 500 | and the Corresponding Source of the work is not available for anyone 501 | to copy, free of charge and under the terms of this License, through a 502 | publicly available network server or other readily accessible means, 503 | then you must either (1) cause the Corresponding Source to be so 504 | available, or (2) arrange to deprive yourself of the benefit of the 505 | patent license for this particular work, or (3) arrange, in a manner 506 | consistent with the requirements of this License, to extend the patent 507 | license to downstream recipients. "Knowingly relying" means you have 508 | actual knowledge that, but for the patent license, your conveying the 509 | covered work in a country, or your recipient's use of the covered work 510 | in a country, would infringe one or more identifiable patents in that 511 | country that you have reason to believe are valid. 512 | 513 | If, pursuant to or in connection with a single transaction or 514 | arrangement, you convey, or propagate by procuring conveyance of, a 515 | covered work, and grant a patent license to some of the parties 516 | receiving the covered work authorizing them to use, propagate, modify 517 | or convey a specific copy of the covered work, then the patent license 518 | you grant is automatically extended to all recipients of the covered 519 | work and works based on it. 520 | 521 | A patent license is "discriminatory" if it does not include within 522 | the scope of its coverage, prohibits the exercise of, or is 523 | conditioned on the non-exercise of one or more of the rights that are 524 | specifically granted under this License. You may not convey a covered 525 | work if you are a party to an arrangement with a third party that is 526 | in the business of distributing software, under which you make payment 527 | to the third party based on the extent of your activity of conveying 528 | the work, and under which the third party grants, to any of the 529 | parties who would receive the covered work from you, a discriminatory 530 | patent license (a) in connection with copies of the covered work 531 | conveyed by you (or copies made from those copies), or (b) primarily 532 | for and in connection with specific products or compilations that 533 | contain the covered work, unless you entered into that arrangement, 534 | or that patent license was granted, prior to 28 March 2007. 535 | 536 | Nothing in this License shall be construed as excluding or limiting 537 | any implied license or other defenses to infringement that may 538 | otherwise be available to you under applicable patent law. 539 | 540 | 12. No Surrender of Others' Freedom. 541 | 542 | If conditions are imposed on you (whether by court order, agreement or 543 | otherwise) that contradict the conditions of this License, they do not 544 | excuse you from the conditions of this License. If you cannot convey a 545 | covered work so as to satisfy simultaneously your obligations under this 546 | License and any other pertinent obligations, then as a consequence you may 547 | not convey it at all. For example, if you agree to terms that obligate you 548 | to collect a royalty for further conveying from those to whom you convey 549 | the Program, the only way you could satisfy both those terms and this 550 | License would be to refrain entirely from conveying the Program. 551 | 552 | 13. Use with the GNU Affero General Public License. 553 | 554 | Notwithstanding any other provision of this License, you have 555 | permission to link or combine any covered work with a work licensed 556 | under version 3 of the GNU Affero General Public License into a single 557 | combined work, and to convey the resulting work. The terms of this 558 | License will continue to apply to the part which is the covered work, 559 | but the special requirements of the GNU Affero General Public License, 560 | section 13, concerning interaction through a network will apply to the 561 | combination as such. 562 | 563 | 14. Revised Versions of this License. 564 | 565 | The Free Software Foundation may publish revised and/or new versions of 566 | the GNU General Public License from time to time. Such new versions will 567 | be similar in spirit to the present version, but may differ in detail to 568 | address new problems or concerns. 569 | 570 | Each version is given a distinguishing version number. If the 571 | Program specifies that a certain numbered version of the GNU General 572 | Public License "or any later version" applies to it, you have the 573 | option of following the terms and conditions either of that numbered 574 | version or of any later version published by the Free Software 575 | Foundation. If the Program does not specify a version number of the 576 | GNU General Public License, you may choose any version ever published 577 | by the Free Software Foundation. 578 | 579 | If the Program specifies that a proxy can decide which future 580 | versions of the GNU General Public License can be used, that proxy's 581 | public statement of acceptance of a version permanently authorizes you 582 | to choose that version for the Program. 583 | 584 | Later license versions may give you additional or different 585 | permissions. However, no additional obligations are imposed on any 586 | author or copyright holder as a result of your choosing to follow a 587 | later version. 588 | 589 | 15. Disclaimer of Warranty. 590 | 591 | THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY 592 | APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT 593 | HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY 594 | OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, 595 | THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR 596 | PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM 597 | IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF 598 | ALL NECESSARY SERVICING, REPAIR OR CORRECTION. 599 | 600 | 16. Limitation of Liability. 601 | 602 | IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING 603 | WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MODIFIES AND/OR CONVEYS 604 | THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY 605 | GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE 606 | USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF 607 | DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD 608 | PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), 609 | EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF 610 | SUCH DAMAGES. 611 | 612 | 17. Interpretation of Sections 15 and 16. 613 | 614 | If the disclaimer of warranty and limitation of liability provided 615 | above cannot be given local legal effect according to their terms, 616 | reviewing courts shall apply local law that most closely approximates 617 | an absolute waiver of all civil liability in connection with the 618 | Program, unless a warranty or assumption of liability accompanies a 619 | copy of the Program in return for a fee. 620 | 621 | END OF TERMS AND CONDITIONS 622 | 623 | How to Apply These Terms to Your New Programs 624 | 625 | If you develop a new program, and you want it to be of the greatest 626 | possible use to the public, the best way to achieve this is to make it 627 | free software which everyone can redistribute and change under these terms. 628 | 629 | To do so, attach the following notices to the program. It is safest 630 | to attach them to the start of each source file to most effectively 631 | state the exclusion of warranty; and each file should have at least 632 | the "copyright" line and a pointer to where the full notice is found. 633 | 634 | {one line to give the program's name and a brief idea of what it does.} 635 | Copyright (C) {year} {name of author} 636 | 637 | This program is free software: you can redistribute it and/or modify 638 | it under the terms of the GNU General Public License as published by 639 | the Free Software Foundation, either version 3 of the License, or 640 | (at your option) any later version. 641 | 642 | This program is distributed in the hope that it will be useful, 643 | but WITHOUT ANY WARRANTY; without even the implied warranty of 644 | MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the 645 | GNU General Public License for more details. 646 | 647 | You should have received a copy of the GNU General Public License 648 | along with this program. If not, see . 649 | 650 | Also add information on how to contact you by electronic and paper mail. 651 | 652 | If the program does terminal interaction, make it output a short 653 | notice like this when it starts in an interactive mode: 654 | 655 | {project} Copyright (C) {year} {fullname} 656 | This program comes with ABSOLUTELY NO WARRANTY; for details type `show w'. 657 | This is free software, and you are welcome to redistribute it 658 | under certain conditions; type `show c' for details. 659 | 660 | The hypothetical commands `show w' and `show c' should show the appropriate 661 | parts of the General Public License. Of course, your program's commands 662 | might be different; for a GUI interface, you would use an "about box". 663 | 664 | You should also get your employer (if you work as a programmer) or school, 665 | if any, to sign a "copyright disclaimer" for the program, if necessary. 666 | For more information on this, and how to apply and follow the GNU GPL, see 667 | . 668 | 669 | The GNU General Public License does not permit incorporating your program 670 | into proprietary programs. If your program is a subroutine library, you 671 | may consider it more useful to permit linking proprietary applications with 672 | the library. If this is what you want to do, use the GNU Lesser General 673 | Public License instead of this License. But first, please read 674 | . 675 | -------------------------------------------------------------------------------- /README.md: -------------------------------------------------------------------------------- 1 | # Ansible Community Images 2 | 3 | Container image definitions meant for [ansible-test](https://www.ansible.com/blog/introduction-to-ansible-test) and [Execution Environments](https://www.ansible.com/blog/whats-new-in-ansible-automation-platform-2-automation-execution-environments). 4 | 5 | ⚠️ **Please note that this repository is very much a proof of concept and a work in progress at this time.** ⚠️ 6 | 7 | ## Important ⚠️ 8 | 9 | Images provided by this repository are tailored for development, testing and CI purposes. 10 | **They are maintained by the community and are not supported by Red Hat**: they can and will break or run out of maintenance. 11 | Do not use these images for production! 12 | 13 | You are encouraged to use (or fork) the examples provided here in order to learn how to build and customize your own images tailored to your needs. 14 | 15 | Thank you! 16 | 17 | ## Contributing 18 | 19 | Issues and pull requests to update or add new images (regardless of operating system or distribution) are welcome! 20 | 21 | Images should ideally be very similar in order to provide a consistent testing experience so please have a look at the existing images before submitting a new one. 22 | -------------------------------------------------------------------------------- /ansible-test/README.md: -------------------------------------------------------------------------------- 1 | # Ansible Community `ansible-test` Images 2 | 3 | ## About ansible-test 4 | 5 | ansible-test provides ways to test ansible itself as well as ansible-core and ansible collections with [unit tests](https://docs.ansible.com/ansible/latest/dev_guide/testing_units.html#testing-units), [sanity tests](https://docs.ansible.com/ansible/latest/dev_guide/testing_sanity.html#testing-sanity) and [integration tests](https://docs.ansible.com/ansible/latest/dev_guide/testing_integration.html#testing-integration). 6 | 7 | Since integration tests can result in changes to a system (such as installing packages or changing files and configuration), it may be preferred to run them inside a container image to avoid making unnecessary changes to the host on which the tests are run. 8 | Container images also happen to be useful and convenient for quickly testing different operating systems and versions of python. 9 | 10 | Some container images are provided and supported by ansible-test, such as the following (from the `devel` branch at time of writing): 11 | 12 | ```bash 13 | ansible-test integration --help 14 | # [...] 15 | target docker images and supported python version (choose one): 16 | base (3.13, 3.8, 3.9, 3.10, 3.11, 3.12) 17 | default (3.13, 3.8, 3.9, 3.10, 3.11, 3.12) 18 | alpine320 (3.12) 19 | fedora40 (3.12) 20 | ubuntu2204 (3.10) 21 | ubuntu2404 (3.12) 22 | {image} # python must be specified for custom images 23 | # [...] 24 | ``` 25 | 26 | ansible-test supports specifying custom images instead and the purpose of this repository is to provide suitable images for it. 27 | 28 | ## Important ⚠️ 29 | 30 | Images provided by this repository are tailored for development, testing and CI purposes. 31 | **They are maintained by the community and are not supported by Red Hat**: they can and will break or run out of maintenance. 32 | Do not use these images for production! 33 | 34 | You are encouraged to use (or fork) the examples provided here in order to learn how to build and customize your own images tailored to your needs. 35 | 36 | Thank you! 37 | 38 | ## Building and using images from this repository 39 | 40 | Example: 41 | 42 | ```bash 43 | dnf -y install podman buildah 44 | ./archlinux/build.sh 45 | 46 | pip install ansible-core --user 47 | git clone https://github.com/ansible-collections/community.general ansible_collections/community/general 48 | cd ansible_collections/community/general 49 | ansible-test integration --python 3.13 --docker localhost/test-image:archlinux ini_file 50 | ``` 51 | 52 | ## Available images 53 | 54 | | image | py27 | py36 | py38 | py39 | py3.10 | py3.11 | py3.12 | py3.13 | Notes | 55 | |-------------------|------|------|------|------|--------|--------|--------|--------|---------------------------------------------| 56 | | [archlinux] | | | | | | | | ✔️ | | 57 | | [debian-bullseye] | | | | ✔️ | | | | | Based on [ubuntu2004 ansible-test image] | 58 | | [debian-bookworm] | | | | | | ✔️ | | | Based on debian-bullseye ansible-test image | 59 | 60 | 61 | Note that these images from only work with ansible-test from ansible-core 2.14.0 or later. 62 | 63 | [archlinux]: https://quay.io/ansible-community/test-image:archlinux 64 | [debian-bullseye]: https://quay.io/ansible-community/test-image:debian-bullseye 65 | [debian-bookworm]: https://quay.io/ansible-community/test-image:debian-bookworm 66 | 67 | [ubuntu2004 ansible-test image]: https://github.com/ansible/distro-test-containers/blob/c4fe28818f5a33b675652637e3057bafe50039ee/ubuntu2004-test-container/Dockerfile 68 | -------------------------------------------------------------------------------- /ansible-test/archlinux/build.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # Builds a archlinux image suitable for use with ansible-test 3 | # Based on the centos8-stream image from this repository 4 | set -ex 5 | 6 | SCRIPT_DIR=$(cd `dirname $0` && pwd -P) 7 | DEPENDENCIES="$(cat ${SCRIPT_DIR}/dependencies.txt | tr '\n' ' ')" 8 | 9 | build=$(buildah from docker.io/library/archlinux:latest) 10 | 11 | buildah run "${build}" -- /bin/bash -c "sed -iE 's/^NoExtract.*locale.*$//g' /etc/pacman.conf" 12 | buildah run "${build}" -- /bin/bash -c "pacman -Syy && pacman-key --init && pacman -S archlinux-keyring --noconfirm && pacman -Su --noconfirm && pacman -S ${DEPENDENCIES} --noconfirm && pacman -Scc --noconfirm" 13 | 14 | # Disable PEP 668 marker 15 | buildah run "${build}" -- /bin/bash -c "rm /usr/lib/python3.13/EXTERNALLY-MANAGED" 16 | 17 | # Extra python dependencies 18 | buildah run --volume ${SCRIPT_DIR}:/tmp/src:z "${build}" -- /bin/bash -c "pip3 install -r /tmp/src/requirements.txt" 19 | 20 | # Ansible-specific setup: Generate new SSH host keys, remove requiretty, set up a default inventory, and start SSH server 21 | buildah run "${build}" -- /bin/bash -c "ssh-keygen -A && sed -i -e 's/^\(Defaults\s*requiretty\)/#--- \1/' /etc/sudoers" 22 | buildah run "${build}" -- /bin/bash -c "mkdir -p /etc/ansible && echo -e '[local]\nlocalhost ansible_connection=local' > /etc/ansible/hosts" 23 | buildah run "${build}" -- /bin/bash -c "systemctl enable sshd" 24 | buildah run "${build}" -- /bin/bash -c "ln -s /usr/share/zoneinfo/UTC /etc/localtime" 25 | buildah run "${build}" -- /bin/bash -c "sed /etc/locale.gen -i -e 's/# *en_US\\.UTF-8/en_US.UTF-8/'" 26 | buildah run "${build}" -- /bin/bash -c "locale-gen" 27 | buildah run "${build}" -- /bin/bash -c "echo 'LANG=en_US.UTF-8' > /etc/locale.conf" 28 | buildah run "${build}" -- /bin/bash -c "systemd-machine-id-setup" 29 | 30 | buildah config --env container=docker "${build}" 31 | buildah config --cmd "/usr/sbin/init" "${build}" 32 | buildah commit "${build}" "${1:-localhost/test-image:archlinux}" 33 | -------------------------------------------------------------------------------- /ansible-test/archlinux/dependencies.txt: -------------------------------------------------------------------------------- 1 | acl 2 | asciidoc 3 | bzip2 4 | coreutils 5 | file 6 | gcc 7 | git 8 | glibc 9 | iproute 10 | libffi 11 | make 12 | net-tools 13 | openssh 14 | python 15 | python-cffi 16 | python-cryptography 17 | python-lxml 18 | python-pip 19 | python-setuptools 20 | python-wheel 21 | rubygems 22 | sshpass 23 | subversion 24 | sudo 25 | unzip 26 | which 27 | -------------------------------------------------------------------------------- /ansible-test/archlinux/requirements.txt: -------------------------------------------------------------------------------- 1 | coverage==6.5.0 2 | # include ara for optional test and CI reporting 3 | ara 4 | -------------------------------------------------------------------------------- /ansible-test/debian-bookworm/build.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # Builds a debian bookworm image suitable for use with ansible-test 3 | # Based on https://github.com/ansible/distro-test-containers/blob/c4fe28818f5a33b675652637e3057bafe50039ee/ubuntu2004-test-container/Dockerfile 4 | set -ex 5 | 6 | SCRIPT_DIR=$(cd `dirname $0` && pwd -P) 7 | DEPENDENCIES="$(cat ${SCRIPT_DIR}/dependencies.txt | tr '\n' ' ')" 8 | 9 | build=$(buildah from docker.io/library/debian:bookworm) 10 | buildah run "${build}" -- /bin/bash -c "apt-get update -y && DEBIAN_FRONTEND=noninteractive apt-get upgrade -y --no-install-recommends && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends ${DEPENDENCIES} && apt-get clean && rm -rf /var/lib/apt/lists/*" 11 | 12 | # Disable PEP 668 marker 13 | buildah run "${build}" -- /bin/bash -c "rm /usr/lib/python3.11/EXTERNALLY-MANAGED" 14 | 15 | # Extra python dependencies 16 | buildah run --volume ${SCRIPT_DIR}:/tmp/src:z "${build}" -- /bin/bash -c "pip3 install -r /tmp/src/requirements.txt" 17 | 18 | # Ansible-specific setup: 19 | buildah run "${build}" -- /bin/bash -c "ln -s /lib/systemd/systemd /sbin/init" 20 | buildah run "${build}" -- /bin/bash -c "rm /etc/apt/apt.conf.d/docker-clean" 21 | buildah run "${build}" -- /bin/bash -c "ssh-keygen -A && sed -i -e 's/^\(Defaults\s*requiretty\)/#--- \1/' /etc/sudoers" 22 | buildah run "${build}" -- /bin/bash -c "mkdir -p /etc/ansible && echo -e '[local]\nlocalhost ansible_connection=local' > /etc/ansible/hosts" 23 | buildah run "${build}" -- /bin/bash -c "sed /etc/locale.gen -i -e 's/# en_US\\.UTF-8/en_US.UTF-8/'" 24 | buildah run "${build}" -- /bin/bash -c "locale-gen" 25 | buildah run "${build}" -- /bin/bash -c "update-locale LANG=en_US.UTF-8" 26 | 27 | buildah config --env container=docker "${build}" 28 | buildah config --cmd "/sbin/init" "${build}" 29 | buildah commit "${build}" "${1:-localhost/test-image:debian-bookworm}" 30 | -------------------------------------------------------------------------------- /ansible-test/debian-bookworm/dependencies.txt: -------------------------------------------------------------------------------- 1 | acl 2 | bzip2 3 | curl 4 | debhelper 5 | debianutils 6 | devscripts 7 | docbook-xml 8 | dpkg-dev 9 | fakeroot 10 | gawk 11 | gcc 12 | git 13 | iproute2 14 | libffi-dev 15 | libssl-dev 16 | libxml2-utils 17 | locales 18 | lsb-release 19 | make 20 | pass 21 | openssh-client 22 | openssh-server 23 | python3-cryptography 24 | python3-dev 25 | python3-dbus 26 | python3-httplib2 27 | python3-jinja2 28 | python3-lxml 29 | python3-mock 30 | python3-nose 31 | python3-packaging 32 | python3-passlib 33 | python3-pip 34 | python3-setuptools 35 | python3-venv 36 | python3-virtualenv 37 | python3-wheel 38 | python3-yaml 39 | reprepro 40 | rsync 41 | ruby 42 | sshpass 43 | subversion 44 | sudo 45 | systemd 46 | tzdata 47 | unzip 48 | virtualenv 49 | xsltproc 50 | zip 51 | -------------------------------------------------------------------------------- /ansible-test/debian-bookworm/requirements.txt: -------------------------------------------------------------------------------- 1 | coverage==6.5.0 2 | resolvelib==0.5.4 3 | # include ara for optional test and CI reporting 4 | ara 5 | -------------------------------------------------------------------------------- /ansible-test/debian-bullseye/build.sh: -------------------------------------------------------------------------------- 1 | #!/bin/bash 2 | # Builds a debian bullseye image suitable for use with ansible-test 3 | # Based on https://github.com/ansible/distro-test-containers/blob/c4fe28818f5a33b675652637e3057bafe50039ee/ubuntu2004-test-container/Dockerfile 4 | set -ex 5 | 6 | SCRIPT_DIR=$(cd `dirname $0` && pwd -P) 7 | DEPENDENCIES="$(cat ${SCRIPT_DIR}/dependencies.txt | tr '\n' ' ')" 8 | 9 | build=$(buildah from docker.io/library/debian:bullseye) 10 | buildah run "${build}" -- /bin/bash -c "apt-get update -y && DEBIAN_FRONTEND=noninteractive apt-get upgrade -y --no-install-recommends && DEBIAN_FRONTEND=noninteractive apt-get install -y --no-install-recommends ${DEPENDENCIES} && apt-get clean && rm -rf /var/lib/apt/lists/*" 11 | 12 | # Extra python dependencies 13 | buildah run --volume ${SCRIPT_DIR}:/tmp/src:z "${build}" -- /bin/bash -c "pip3 install -r /tmp/src/requirements.txt" 14 | 15 | # Ansible-specific setup: 16 | buildah run "${build}" -- /bin/bash -c "ln -s /lib/systemd/systemd /sbin/init" 17 | buildah run "${build}" -- /bin/bash -c "rm /etc/apt/apt.conf.d/docker-clean" 18 | buildah run "${build}" -- /bin/bash -c "ssh-keygen -A && sed -i -e 's/^\(Defaults\s*requiretty\)/#--- \1/' /etc/sudoers" 19 | buildah run "${build}" -- /bin/bash -c "mkdir -p /etc/ansible && echo -e '[local]\nlocalhost ansible_connection=local' > /etc/ansible/hosts" 20 | buildah run "${build}" -- /bin/bash -c "sed /etc/locale.gen -i -e 's/# en_US\\.UTF-8/en_US.UTF-8/'" 21 | buildah run "${build}" -- /bin/bash -c "locale-gen" 22 | buildah run "${build}" -- /bin/bash -c "update-locale LANG=en_US.UTF-8" 23 | 24 | buildah config --env container=docker "${build}" 25 | buildah config --cmd "/sbin/init" "${build}" 26 | buildah commit "${build}" "${1:-localhost/test-image:debian-bullseye}" 27 | -------------------------------------------------------------------------------- /ansible-test/debian-bullseye/dependencies.txt: -------------------------------------------------------------------------------- 1 | acl 2 | bzip2 3 | curl 4 | debhelper 5 | debianutils 6 | devscripts 7 | docbook-xml 8 | dpkg-dev 9 | fakeroot 10 | gawk 11 | gcc 12 | git 13 | iproute2 14 | libffi-dev 15 | libssl-dev 16 | libxml2-utils 17 | locales 18 | lsb-release 19 | make 20 | pass 21 | openssh-client 22 | openssh-server 23 | python3-cryptography 24 | python3-dev 25 | python3-dbus 26 | python3-httplib2 27 | python3-jinja2 28 | python3-lxml 29 | python3-mock 30 | python3-nose 31 | python3-packaging 32 | python3-passlib 33 | python3-pip 34 | python3-setuptools 35 | python3-venv 36 | python3-virtualenv 37 | python3-wheel 38 | python3-yaml 39 | reprepro 40 | rsync 41 | ruby 42 | sshpass 43 | subversion 44 | sudo 45 | systemd 46 | tzdata 47 | unzip 48 | virtualenv 49 | xsltproc 50 | zip 51 | -------------------------------------------------------------------------------- /ansible-test/debian-bullseye/requirements.txt: -------------------------------------------------------------------------------- 1 | coverage==6.5.0 2 | resolvelib==0.5.4 3 | # include ara for optional test and CI reporting 4 | ara 5 | -------------------------------------------------------------------------------- /docs/community-ee/community-ee-announcement.md: -------------------------------------------------------------------------------- 1 | # Forum Announcement 2 | 3 | Release announcement to be done in the Ecosystem Release sub-category under the News & Announcements category. Follow [forum link](https://forum.ansible.com/c/news/releases/18) to create the announcement post. 4 | 5 | ``` 6 | Hello everyone, 7 | 8 | We’re happy to announce the release of the 9 | 10 | Ansible Community Execution Environment Minimal and Ansible Community Execution Environment Base ! 11 | 12 | ## What are Execution Environments? 13 | 14 | Read the [Getting started with Execution Environments](https://docs.ansible.com/ansible/devel/getting_started_ee/index.html) guide to learn how to benefit from running Ansible automation in containers. 15 | 16 | ## What's inside community-ee-minimal ? 17 | 18 | Ansible community-ee-minimal is a container image. It includes: 19 | 20 | - `base_image`: fedora-minimal 21 | 22 | - `ansible-core`: 23 | 24 | - `collections`: The following set of collections 25 | 26 | - ansible.posix 27 | - ansible.utils 28 | - ansible.windows 29 | 30 | ## sha256 sum value of the container image: 31 | 32 | 33 | ## How to get community-ee-minimal? 34 | 35 | ### Install from command line via @sha256_sum_value of the image 36 | 37 | `podman pull http://ghcr.io/ansible-community/community-ee-minimal@sha256:` 38 | 39 | ### Install from command line via image tag 40 | 41 | `podman pull ghcr.io/ansible-community/community-ee-minimal:latest` 42 | `podman pull ghcr.io/ansible-community/community-ee-minimal:` 43 | 44 | 45 | ## What's inside community-ee-base? 46 | 47 | - `base_image`: fedora-minimal 48 | 49 | - `ansible-core`: ansible-core 50 | 51 | ## sha256 sum value of the container image: 52 | 53 | 54 | 55 | ## How to get community-ee-base? 56 | 57 | ### Install from command line via @sha256_sum_value of the image 58 | 59 | `podman pull http://ghcr.io/ansible-community/community-ee-base@sha256:` 60 | 61 | ### Install from command line via image tag 62 | 63 | `podman pull ghcr.io/ansible-community/community-ee-base:latest` 64 | `podman pull ghcr.io/ansible-community/community-ee-base:` 65 | 66 | 67 | ## To know about future releases 68 | 69 | Join the [Ansible Community Forum](https://forum.ansible.com) to follow along and participate 70 | in all the discussions. 71 | 72 | Subscribe to the [Bullhorn](https://forum.ansible.com/c/news/bullhorn/17) for all future release dates, announcements, and Ansible community contributor news. 73 | 74 | On behalf of the Ansible community, thank you and happy automating! 75 | 76 | Cheers, 77 | Ansible Community Team 78 | 79 | ``` 80 | 81 | ## Matrix Announcement 82 | 83 | Inform the Ansible users - Matrix: #users:ansible.com 84 | 85 | Inform Discussions on community and collections related topics - Matrix: #community:ansible.com 86 | 87 | Inform the Release Managers Working Group: Matrix: #release-management:ansible.com 88 | 89 | Inform Community social room - Matrix: #social:ansible.com 90 | Posting news for the Bullhorn newsletter @newsbot 91 | 92 | 93 | ``` 94 | We’re happy to announce the release of the 95 | 96 | Ansible Community Execution Environment Minimal and Ansible Community Execution Environment Base ! 97 | 98 | Get the details of both the images [in the forum post](). 99 | 100 | On behalf of the Ansible community, thank you and happy automating! 101 | 102 | ``` 103 | 104 | 105 | ## Bullhorn Announcement 106 | We’re happy to announce the release of the Ansible Community Execution Environment Minimal image (Latest) and Ansible Community Execution Environment Base image . 107 | 108 | Read the whole announcement [in the ansible forum](link to forum announcement). 109 | 110 | -------------------------------------------------------------------------------- /docs/community-ee/community-ee-release-process.md: -------------------------------------------------------------------------------- 1 | # Releasing community-ee-* execution environments 2 | 3 | ## Release Cadence 4 | 5 | The community EEs are built and published on the day after `ansible-core` is released. 6 | 7 | ## EE tag versioning 8 | 9 | The EE versioning convention is core tag plus patch number, for example: 10 | 11 | - EE with core `2.16.2` comes out -> `community-ee:2.16.2-1` 12 | - EE with core `2.16.3` comes out -> `community-ee:2.16.3-1` 13 | 14 | ## Dependencies 15 | 16 | - Podman/Docker 17 | 18 | ## Credentials 19 | 20 | - Access to the https://github.com/ansible-community/images repository 21 | - Access to ghcr.io 22 | 23 | ## Prerequisites 24 | 25 | - Join the [Release Management working group](https://forum.ansible.com/g/release-managers) and [Execution Environment group](https://forum.ansible.com/g/ExecutionEnvs). 26 | - Understand [Ansible execution environments](https://forum.ansible.com/t/execution-environments-getting-started-guide-community-ee-images-availability/1341). 27 | - Read about the [eerelease.yml](/.github/workflows/eerelease.yml) GitHub workflow. 28 | - Show intention and book the date for the releasing of the EE. 29 | 30 | ## Making the pre-release announcement 31 | 32 | Post this message in the channel before working on the release, using the correct release number. 33 | 34 | ```markdown 35 | 📯📯📯 I am working on the `Ansible Execution Environment Base and Minimal 2.x.y-1` Release. I will keep the room updated about the progress.📦️ 36 | ``` 37 | 38 | ## Building the EEs 39 | 40 | ### On the terminal 41 | 42 | 1. Check the most recent [ansible-core version](https://pypi.org/project/ansible-core/) 43 | 2. Verify Ansible collection versions for ``ansible.posix``, ``ansible.utils`` and ``ansible.windows`` for `deps` file of the Ansible community package version for the related release in the [ansible-build-data repo](https://github.com/ansible-community/ansible-build-data). 44 | 3. Change to the `images/execution-environments` directory. 45 | 4. Create a `git branch` that has a name corresponding to the version, for example: `2.17.1-1`. 46 | 47 | ```bash 48 | cd images/execution-environments 49 | git checkout main 50 | git pull upstream main 51 | git checkout -b coreversion-eeversion 52 | ``` 53 | 54 | 5. Update the `ansible-core` and collection versions in the `/images/execution-environments/community-ee-base/execution-environment.yml` file. 55 | 6. Update the `ansible-core` version in the `/images/execution-environments/community-ee-minimal/execution-environment.yml` file. 56 | 7. Commit the changes and create a PR. 57 | 58 | ```bash 59 | vim community-ee-base/execution-environment.yml 60 | git add -u 61 | git status 62 | git commit -m "Updates ansible-core & collection versions for Base and Minimal" 63 | git push origin branch_name 64 | ``` 65 | 66 | After the PR is merged, it is the time to trigger the release workflow on GitHub. 67 | 68 | ### Triggering the release workflow 69 | 70 | 1. Go to the [ansible-community/images](https://github.com/ansible-community/images) repository. 71 | 2. Click the `Actions` tab to view the available workflows. 72 | 3. Go to the `Release Ansible Execution Environment` workflow and then select `Run Workflow`. 73 | 4. Click the drop-down button and choose the type of the Execution Environment, whether `community-ee-base` or `community-ee-minimal`. 74 | 5. Provide the patch number of the execution environment that is appended to the `ansible-core` version, which is typically `1`. 75 | 6. Select the button if this is `latest` release of the particular execution environment. 76 | 7. Click the `Run workflow` to run the workflow. 77 | 8. After the successful run of the workflow, check if the [image is published](https://github.com/orgs/ansible-community/packages/container) and get the sha256 sum of the published image for the release announcement. 78 | 9. Announce the release in the #release-management and #community-working-group Matrix room, Forum, and Bullhorn according to the instructions in `docs/community-ee/community-ee-announcement.md`. 79 | -------------------------------------------------------------------------------- /execution-environments/README.md: -------------------------------------------------------------------------------- 1 | # Ansible Community Execution Environment Images 2 | 3 | ## About Execution Environments 4 | 5 | Execution environments (EE) are container images from which your Ansible commands and playbooks run from. 6 | They are meant to include the Ansible collections, packages and dependencies you need for running Ansible modules and playbooks. 7 | 8 | They can be used by [AWX](https://github.com/ansible/awx), [Automation Controller](https://docs.ansible.com/automation-controller/latest/html/administration/index.html) (previously known as Tower) and [ansible-navigator](https://github.com/ansible/ansible-navigator). 9 | 10 | They can be built using [ansible-builder](https://github.com/ansible/ansible-builder/) with either [docker or podman](https://ansible-builder.readthedocs.io/en/latest/usage/#container-runtime) using [execution environment definitions](https://ansible-builder.readthedocs.io/en/latest/definition/) provided by this repository. 11 | 12 | ## Important ⚠️ 13 | 14 | Images provided by this repository are tailored for development, testing and CI purposes. 15 | **They are maintained by the community and are not supported by Red Hat**: they can and will break or run out of maintenance. 16 | Do not use these images for production! 17 | 18 | You are encouraged to use (or fork) the examples provided here in order to learn how to build and customize your own images tailored to your needs. 19 | 20 | Thank you! 21 | 22 | ## Building and using images from this repository 23 | 24 | Example: 25 | 26 | ```bash 27 | dnf -y install podman 28 | pip install --user ansible-builder ansible-navigator 29 | 30 | cd community-ee-base 31 | 32 | ansible-builder build -v 3 -t community-ee-base:latest 33 | 34 | ansible-navigator -v --pull-policy never \ 35 | --execution-environment-image community-ee-base:latest \ 36 | run tests.yml 37 | ``` 38 | 39 | ## Available images 40 | 41 | - [community-ee-minimal](https://github.com/orgs/ansible-community/packages/container/package/community-ee-minimal): ansible-core with no collections 42 | - [community-ee-base](https://github.com/orgs/ansible-community/packages/container/package/community-ee-base): ansible-core together with `ansible.posix`, `ansible.utils`, and `ansible.windows` 43 | -------------------------------------------------------------------------------- /execution-environments/community-ee-base/execution-environment.yml: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | version: 3 4 | images: 5 | base_image: 6 | name: quay.io/fedora/fedora:41 7 | dependencies: 8 | ansible_core: 9 | package_pip: ansible-core==2.18.5 10 | ansible_runner: 11 | package_pip: ansible-runner 12 | system: 13 | - openssh-clients 14 | - sshpass 15 | - less 16 | galaxy: 17 | collections: 18 | - name: ansible.posix 19 | version: 1.6.2 20 | - name: ansible.utils 21 | version: 5.1.2 22 | - name: ansible.windows 23 | version: 2.8.0 24 | 25 | additional_build_steps: 26 | prepend_base: 27 | - RUN dnf install -y python3 python3-pip python3-libdnf5 28 | -------------------------------------------------------------------------------- /execution-environments/community-ee-base/tests.yml: -------------------------------------------------------------------------------- 1 | - name: Basic integration tests 2 | hosts: localhost 3 | gather_facts: false 4 | pre_tasks: 5 | - name: Collect some facts 6 | ansible.builtin.setup: 7 | gather_subset: 8 | - "!all" 9 | - "!any" 10 | - date_time 11 | - distribution 12 | - dns 13 | - kernel 14 | - python 15 | 16 | - name: Install ps 17 | become: true 18 | ansible.builtin.package: # noqa package-latest 19 | name: procps-ng 20 | state: latest 21 | 22 | - name: Print running Ansible processes 23 | ansible.builtin.shell: | 24 | set -o pipefail 25 | ps fauxwww | grep -i ansible 26 | changed_when: false 27 | 28 | - name: Retrieve the installed version of ansible-core with pip 29 | ansible.builtin.shell: | 30 | set -o pipefail 31 | pip show ansible-core | awk '/^Version/ {print $2}' 32 | changed_when: false 33 | register: _installed_ansible_core 34 | 35 | - name: Retrieve the installed version of ansible-runner with pip 36 | ansible.builtin.shell: | 37 | set -o pipefail 38 | pip show ansible-runner | awk '/^Version/ {print $2}' 39 | changed_when: false 40 | register: _installed_ansible_runner 41 | 42 | - name: Retrieve the installed version of ansible 43 | ansible.builtin.shell: | 44 | set -o pipefail 45 | ansible --version | awk '/core/ { gsub("]",""); print $3 }' 46 | changed_when: false 47 | register: _ansible_version 48 | 49 | - name: Installing less should be a no-op 50 | become: true 51 | ansible.builtin.package: # noqa package-latest 52 | name: less 53 | state: latest 54 | register: _installed_less 55 | 56 | tasks: 57 | - name: Validate image 58 | ansible.builtin.assert: 59 | that: 60 | - ansible_distribution == "Fedora" 61 | - ansible_distribution_release == "" 62 | - ansible_distribution_version | int >= 38 63 | - _installed_ansible_core.stdout == _ansible_version.stdout 64 | - _installed_ansible_runner.stdout is version('2.4.1', '>=') 65 | - _installed_less.changed == false 66 | -------------------------------------------------------------------------------- /execution-environments/community-ee-minimal/execution-environment.yml: -------------------------------------------------------------------------------- 1 | --- 2 | 3 | version: 3 4 | images: 5 | base_image: 6 | name: quay.io/fedora/fedora:41 7 | dependencies: 8 | ansible_core: 9 | package_pip: ansible-core==2.18.5 10 | ansible_runner: 11 | package_pip: ansible-runner 12 | system: 13 | - openssh-clients 14 | - sshpass 15 | - less 16 | 17 | additional_build_steps: 18 | prepend_base: 19 | - RUN dnf install -y python3 python3-pip python3-libdnf5 20 | -------------------------------------------------------------------------------- /execution-environments/community-ee-minimal/tests.yml: -------------------------------------------------------------------------------- 1 | - name: Basic integration tests 2 | hosts: localhost 3 | gather_facts: false 4 | pre_tasks: 5 | - name: Collect some facts 6 | ansible.builtin.setup: 7 | gather_subset: 8 | - "!all" 9 | - "!any" 10 | - date_time 11 | - distribution 12 | - dns 13 | - kernel 14 | - python 15 | 16 | - name: Install ps 17 | become: true 18 | ansible.builtin.package: # noqa package-latest 19 | name: procps-ng 20 | state: latest 21 | 22 | - name: Print running Ansible processes 23 | ansible.builtin.shell: | 24 | set -o pipefail 25 | ps fauxwww | grep -i ansible 26 | changed_when: false 27 | 28 | - name: Retrieve the installed version of ansible-core with pip 29 | ansible.builtin.shell: | 30 | set -o pipefail 31 | pip show ansible-core | awk '/^Version/ {print $2}' 32 | changed_when: false 33 | register: _installed_ansible_core 34 | 35 | - name: Retrieve the installed version of ansible-runner with pip 36 | ansible.builtin.shell: | 37 | set -o pipefail 38 | pip show ansible-runner | awk '/^Version/ {print $2}' 39 | changed_when: false 40 | register: _installed_ansible_runner 41 | 42 | - name: Retrieve the installed version of ansible 43 | ansible.builtin.shell: | 44 | set -o pipefail 45 | ansible --version | awk '/core/ { gsub("]",""); print $3 }' 46 | changed_when: false 47 | register: _ansible_version 48 | 49 | - name: Installing less should be a no-op 50 | become: true 51 | ansible.builtin.package: # noqa package-latest 52 | name: less 53 | state: latest 54 | register: _installed_less 55 | 56 | tasks: 57 | - name: Validate image 58 | ansible.builtin.assert: 59 | that: 60 | - ansible_distribution == "Fedora" 61 | - ansible_distribution_release == "" 62 | - ansible_distribution_version | int >= 38 63 | - _installed_ansible_core.stdout == _ansible_version.stdout 64 | - _installed_ansible_runner.stdout is version('2.4.1', '>=') 65 | - _installed_less.changed == false 66 | --------------------------------------------------------------------------------