Build/Test Tools: Remove unnecessary docker branding

Author: Ninos

.devcontainer/devcontainer.json

@@ -1,7 +1,7 @@
 // For format details, see https://aka.ms/devcontainer.json.
 {
     "name": "WordPress Core Development",
-    "dockerComposeFile": "docker-compose.yml",
+    "dockerComposeFile": "compose.yml",
     "service": "app",
     "workspaceFolder": "/workspace",
 

.github/workflows/local-docker-environment.yml

@@ -9,7 +9,7 @@ on:
     paths:
       # Any changes to Docker related files.
       - '.env.example'
-      - 'docker-compose.yml'
+      - 'compose.yml'
       # Any changes to local environment related files
       - 'tools/local-env/**'
       # These files configure npm and the task runner. Changes could affect the outcome.
@@ -33,7 +33,7 @@ on:
     paths:
       # Any changes to Docker related files.
       - '.env.example'
-      - 'docker-compose.yml'
+      - 'compose.yml'
       # Any changes to local environment related files
       - 'tools/local-env/**'
       # These files configure npm and the task runner. Changes could affect the outcome.

.github/workflows/test-coverage.yml

@@ -8,7 +8,7 @@ on:
     paths:
       - '.github/workflows/test-coverage.yml'
       - '.github/workflows/reusable-phpunit-tests-v3.yml'
-      - 'docker-compose.yml'
+      - 'compose.yml'
       - 'phpunit.xml.dist'
       - 'tests/phpunit/multisite.xml'
   pull_request:
@@ -17,7 +17,7 @@ on:
     paths:
       - '.github/workflows/test-coverage.yml'
       - '.github/workflows/reusable-phpunit-tests-v3.yml'
-      - 'docker-compose.yml'
+      - 'compose.yml'
       - 'phpunit.xml.dist'
       - 'tests/phpunit/multisite.xml'
   # Once daily at 00:00 UTC.

.gitignore

@@ -103,7 +103,7 @@ wp-tests-config.php
 !/src/js/_enqueues/vendor
 
 # Files for local environment config
-/docker-compose.override.yml
+/compose.override.yml
 
 # Visual regression test diffs
 tests/visual-regression/specs/__snapshots__

README.md

@@ -37,11 +37,11 @@ If you are not using a package manager, see the [Node.js download page](https://
 
 **Note:** WordPress currently only officially supports Node.js `20.x` and npm `10.x`.
 
-You will also need [Docker](https://www.docker.com/products/docker-desktop) installed and running on your computer. Docker is the virtualization software that powers the local development environment. Docker can be installed just like any other regular application.
+You will also need a container environment (e.g. [Docker](https://www.docker.com/products/docker-desktop) or [Podman](https://podman-desktop.io/)) installed and running on your computer. The container environment is the virtualization software that powers the local development environment. Both applications can be installed just like any other regular application.
 
 ### Development Environment Commands
 
-Ensure [Docker](https://www.docker.com/products/docker-desktop) is running before using these commands.
+Ensure either [Docker](https://www.docker.com/products/docker-desktop) or [Podman](https://podman-desktop.io/) are running before using these commands.
 
 #### To start the development environment for the first time
 
@@ -97,7 +97,7 @@ npm run test:php -- --group <group name or ticket number>
 #### Generating a code coverage report
 PHP code coverage reports are [generated daily](https://github.com/WordPress/wordpress-develop/actions/workflows/test-coverage.yml) and [submitted to Codecov.io](https://app.codecov.io/gh/WordPress/wordpress-develop).
 
-After the local Docker environment has [been installed and started](#to-start-the-development-environment-for-the-first-time), the following command can be used to generate a code coverage report. 
+After the local container environment has [been installed and started](#to-start-the-development-environment-for-the-first-time), the following command can be used to generate a code coverage report. 
 
 ```
 npm run test:coverage
@@ -109,7 +109,7 @@ The command will generate three coverage reports in HTML, PHP, and text formats,
 
 #### To restart the development environment
 
-You may want to restart the environment if you've made changes to the configuration in the `docker-compose.yml` or `.env` files. Restart the environment with:
+You may want to restart the environment if you've made changes to the configuration in the `compose.yml` or `.env` files. Restart the environment with:
 
 ```
 npm run env:restart
@@ -133,20 +133,20 @@ npm run env:start
 
 #### Resetting the development environment
 
-The development environment can be reset. This will destroy the database and attempt to remove the pulled Docker images.
+The development environment can be reset. This will destroy the database and attempt to remove the pulled container images.
 
 ```
 npm run env:reset
 ```
 
 ### Apple Silicon machines and old MySQL/MariaDB versions
 
-Older MySQL and MariaDB Docker images do not support Apple Silicon processors (M1, M2, etc.). This is true for:
+Older MySQL and MariaDB container images do not support Apple Silicon processors (M1, M2, etc.). This is true for:
 
 - MySQL versions 5.7 and earlier
 - MariaDB 5.5
 
-When using these versions on an Apple Silicon machine, you must create a `docker-compose.override.yml` file with the following contents:
+When using these versions on an Apple Silicon machine, you must create a `compose.override.yml` file with the following contents:
 
 ```
 services:
@@ -155,7 +155,7 @@ services:
     platform: linux/amd64
 ```
 
-Additionally, the "Use Rosetta for x86/AMD64 emulation on Apple Silicon" setting in Docker needs to be disabled for this workaround.
+Additionally, the "Use Rosetta for x86/AMD64 emulation on Apple Silicon" setting in containers needs to be disabled for this workaround.
 
 ## Credentials
 

docker-compose.yml compose.ymldocker-compose.yml renamed to compose.yml

@@ -4,7 +4,7 @@ services:
   # The web server container.
   ##
   wordpress-develop:
-    image: nginx:alpine
+    image: docker.io/nginx:alpine
 
     networks:
       - wpdevnet
@@ -32,7 +32,7 @@ services:
   # The PHP container.
   ##
   php:
-    image: wordpressdevelop/php:${LOCAL_PHP-latest}
+    image: docker.io/wordpressdevelop/php:${LOCAL_PHP-latest}
 
     networks:
       - wpdevnet
@@ -64,7 +64,7 @@ services:
   # The MySQL container.
   ##
   mysql:
-    image: ${LOCAL_DB_TYPE-mysql}:${LOCAL_DB_VERSION-latest}
+    image: docker.io/${LOCAL_DB_TYPE-mysql}:${LOCAL_DB_VERSION-latest}
 
     networks:
       - wpdevnet
@@ -95,7 +95,7 @@ services:
   # The WP CLI container.
   ##
   cli:
-    image: wordpressdevelop/cli:${LOCAL_PHP-latest}
+    image: docker.io/wordpressdevelop/cli:${LOCAL_PHP-latest}
 
     networks:
       - wpdevnet
@@ -130,7 +130,7 @@ services:
   # The Memcached container.
   ##
   memcached:
-    image: memcached
+    image: docker.io/memcached:latest
 
     networks:
       - wpdevnet

tools/local-env/scripts/utils.js

@@ -8,18 +8,18 @@ const local_env_utils = {
 	 * Determines which Docker compose files are required to properly configure the local environment given the
 	 * specified PHP version, database type, and database version.
 	 *
-	 * By default, only the standard docker-compose.yml file will be used.
+	 * By default, only the standard compose.yml file will be used.
 	 *
 	 * When PHP 7.2 or 7.3 is used in combination with MySQL 8.4, an override file will also be returned to ensure
 	 * that the mysql_native_password plugin authentication plugin is on and available for use.
 	 *
 	 * @return {string[]} Compose files.
 	 */
 	get_compose_files: function() {
-		const composeFiles = [ 'docker-compose.yml' ];
+		const composeFiles = [ 'compose.yml' ];
 
-		if ( existsSync( 'docker-compose.override.yml' ) ) {
-			composeFiles.push( 'docker-compose.override.yml' );
+		if ( existsSync( 'compose.override.yml' ) ) {
+			composeFiles.push( 'compose.override.yml' );
 		}
 
 		if ( process.env.LOCAL_DB_TYPE !== 'mysql' ) {