publish updates from main (#22321)

Automated pull request for publishing docs updates.

---------

Signed-off-by: Craig <[email protected]>
Signed-off-by: CrazyMax <[email protected]>
Signed-off-by: Lorena Rangel <[email protected]>
Co-authored-by: aevesdocker <[email protected]>
Co-authored-by: Allie Sadler <[email protected]>
Co-authored-by: Andrey Sobolev <[email protected]>
Co-authored-by: Sarah Sanders <[email protected]>
Co-authored-by: Bokyeom <[email protected]>
Co-authored-by: Craig Osterhout <[email protected]>
Co-authored-by: Marco Franzon <[email protected]>
Co-authored-by: CrazyMax <[email protected]>
Co-authored-by: yinzhidong <[email protected]>
Co-authored-by: Lorena Rangel <[email protected]>

Author: 9 people

_vale/config/vocabularies/Docker/accept.txt

@@ -20,6 +20,7 @@ Datadog
 Ddosify
 Debootstrap
 Dev
+Dex
 Dev Environments?
 Django
 Docker Build Cloud

content/get-started/docker-concepts/running-containers/overriding-container-defaults.md

@@ -71,7 +71,7 @@ In this hands-on guide, you'll see how to use the `docker run` command to overri
 
 1. [Download and install](/get-started/get-docker/) Docker Desktop.
 
-### Run multiple instance of the Postgres database
+### Run multiple instances of the Postgres database
 
 1.  Start a container using the [Postgres image](https://hub.docker.com/_/postgres) with the following command:
 

content/guides/databases.md

@@ -78,8 +78,8 @@ To run a container using the GUI:
 1. In the Docker Desktop Dashboard, select the global search at the top of the window.
 2. Specify `mysql` in the search box, and select the `Images` tab if not already
    selected.
-3. Hover over the `msyql` image and select `Run`.
-   The **Run a new container** model appears.
+3. Hover over the `mysql` image and select `Run`.
+   The **Run a new container** modal appears.
 4. Expand **Optional settings**.
 5. In the optional settings, specify the following:
 
@@ -181,7 +181,7 @@ interact with your MySQL database.
 Before you begin, you must remove any containers you previously ran for this
 guide. To stop and remove a container, either:
 
-- In a terminal, run `docker remove --force my-mysql` to remove the container
+- In a terminal, run `docker rm --force my-mysql` to remove the container
   named `my-mysql`.
 - Or, in the Docker Desktop Dashboard, select the **Delete** icon next to your
   container in the **Containers** view.
@@ -221,8 +221,8 @@ To run a container using the GUI:
 1. In the Docker Desktop Dashboard, select the global search at the top of the window.
 2. Specify `mysql` in the search box, and select the `Images` tab if not already
    selected.
-3. Hover over the `msyql` image and select `Run`.
-   The **Run a new container** model appears.
+3. Hover over the `mysql` image and select `Run`.
+   The **Run a new container** modal appears.
 4. Expand **Optional settings**.
 5. In the optional settings, specify the following:
 
@@ -392,7 +392,7 @@ data persists:
    2. Specify `mysql` in the search box, and select the **Images** tab if not
       already selected.
    3. Hover over the **mysql** image and select **Run**.
-      The **Run a new container** model appears.
+      The **Run a new container** modal appears.
    4. Expand **Optional settings**.
    5. In the optional settings, specify the following:
 
@@ -433,7 +433,7 @@ data persists:
    2. Specify `mysql` in the search box, and select the **Images** tab if not
       already selected.
    3. Hover over the **mysql** image and select **Run**.
-      The **Run a new container** model appears.
+      The **Run a new container** modal appears.
    4. Expand **Optional settings**.
    5. In the optional settings, specify the following:
 

content/guides/dex.md

@@ -0,0 +1,169 @@
+---
+title: Mocking OAuth services in testing with Dex
+description: &desc Mocking OAuth services in testing with Dex
+keywords: Dex, container-supported development
+linktitle: Mocking OAuth services with Dex
+summary: *desc
+tags: [app-dev, distributed-systems]
+languages: []
+params:
+  time: 10 minutes
+---
+
+Dex is an open-source OpenID Connect (OIDC) and OAuth 2.0 identity provider that can be configured to authenticate against various backend identity providers, such as LDAP, SAML, and OAuth. Running Dex in a Docker container allows developers to simulate an OAuth 2.0 server for testing and development purposes. This guide will walk you through setting up Dex as an OAuth mock server using Docker containers.
+
+Nowadays OAuth is the preferred choice to authenticate in web services, the highest part of them give the possibility to access using popular OAuth services like GitHub, Google or Apple. Using OAuth guarantees a higher level of security and simplification since it is not necessary to create new profiles for each service. This means that, by allowing applications to access resources on behalf of users without sharing passwords, OAuth minimizes the risk of credential exposure.
+
+In this guide, you'll learn how to:
+
+- Use Docker to launch up a Dex container.
+- Use mock OAuth in the GitHub Action (GHA) without relying on an external OAuth provider.
+
+## Using Dex with Docker
+
+The official [Docker image for Dex](https://hub.docker.com/r/dexidp/dex/) provides a convenient way to deploy and manage Dex instances. Dex is available for various CPU architectures, including amd64, armv7, and arm64, ensuring compatibility with different devices and platforms. You can learn more about Dex standalone on the [Dex docs site](https://dexidp.io/docs/getting-started/).
+
+### Prerequisites
+
+[Docker Compose](/compose/): Recommended for managing multi-container Docker applications.
+
+### Setting Up Dex with Docker
+
+Begin by creating a directory for your Dex project:
+
+```bash
+mkdir dex-mock-server
+cd dex-mock-server
+```
+Organize your project with the following structure:
+
+```bash
+dex-mock-server/
+├── config.yaml
+└── compose.yaml
+```
+
+Create the Dex Configuration File:
+The config.yaml file defines Dex's settings, including connectors, clients, and storage. For a mock server setup, you can use the following minimal configuration:
+
+```yaml
+# config.yaml
+issuer: http://localhost:5556/dex
+storage:
+  type: memory
+web:
+  http: 0.0.0.0:5556
+staticClients:
+  - id: example-app
+    redirectURIs:
+      - 'http://localhost:5555/callback'
+    name: 'Example App'
+    secret: ZXhhbXBsZS1hcHAtc2VjcmV0
+enablePasswordDB: true
+staticPasswords:
+  - email: "[email protected]"
+    hash: "$2a$10$2b2cU8CPhOTaGrs1HRQuAueS7JTT5ZHsHSzYiFPm1leZck7Mc8T4W"
+    username: "admin"
+    userID: "1234"
+```
+
+Explanation:
+- issuer: The public URL of Dex.
+
+- storage: Using in-memory storage for simplicity.
+
+- web: Dex will listen on port 5556.
+
+- staticClients: Defines a client application (example-app) with its redirect URI and secret.
+
+- enablePasswordDB: Enables static password authentication.
+
+- staticPasswords: Defines a static user for authentication. The hash is a bcrypt hash of the password.
+
+> [!NOTE]
+>
+> Ensure the hash is a valid bcrypt hash of your desired password. You can generate this using tools like [bcrypt-generator.com](https://bcrypt-generator.com/).
+or use CLI tools like [htpasswd](https://httpd.apache.org/docs/2.4/programs/htpasswd.html) like in this following example:`echo password | htpasswd -BinC 10 admin | cut -d: -f2`
+
+With Docker Compose configured, start Dex:
+```yaml
+# docker-compose.yaml
+
+services:
+  dex:
+    image: dexidp/dex:latest
+    container_name: dex
+    ports:
+      - "5556:5556"
+    volumes:
+      - ./config.yaml:/etc/dex/config.yaml
+    command: ["dex", "serve", "/etc/dex/config.yaml"]
+```
+
+Now it is possible to run the container using the `docker compose` command.
+```bash
+docker compose up -d
+```
+
+This command will download the Dex Docker image (if not already available) and start the container in detached mode.
+
+
+To verify that Dex is running, check the logs to ensure Dex started successfully:
+```bash
+docker compose logs -f dex
+```
+You should see output indicating that Dex is listening on the specified port.
+
+### Using Dex OAuth testing in GHA
+
+To test the OAuth flow, you'll need a client application configured to authenticate against Dex. One of the most typical use cases is to use it inside GitHub Actions. Since Dex supports mock authentication, you can predefine test users as suggested in the [docs](https://dexidp.io/docs). The `config.yaml` file should looks like:
+
+```yaml
+issuer: http://127.0.0.1:5556/dex
+
+storage:
+  type: memory
+
+web:
+  http: 0.0.0.0:5556
+
+oauth2:
+  skipApprovalScreen: true
+
+staticClients:
+  - name: TestClient
+    id: client_test_id
+    secret: client_test_secret
+    redirectURIs:
+      - http://{ip-your-app}/path/to/callback/ # example: http://localhost:5555/callback
+
+connectors:
+# mockCallback connector always returns the user '[email protected]'.
+- type: mockCallback
+  id: mock
+  name: Mock
+```
+Now you can insert the Dex service inside your `~/.github/workflows/ci.yaml` file:
+
+```yaml
+[...]
+jobs:
+  test-oauth:
+    runs-on: ubuntu-latest
+    steps:
+      - name: Install Dex
+        run: |
+          curl -L https://github.com/dexidp/dex/releases/download/v2.37.0/dex_linux_amd64 -o dex
+          chmod +x dex
+
+      - name: Start Dex Server
+        run: |
+          nohup ./dex serve config.yaml > dex.log 2>&1 &
+          sleep 5  # Give Dex time to start
+[...]
+```
+
+
+### Conclusion
+
+By following this guide, you've set up Dex as an OAuth mock server using Docker. This setup is invaluable for testing and development, allowing you to simulate OAuth flows without relying on external identity providers. For more advanced configurations and integrations, refer to the [Dex documentation](https://dexidp.io/docs/).

content/guides/golang/develop.md

@@ -521,7 +521,7 @@ In this section, you'll create a Docker Compose file to start your `docker-gs-pi
 
 ### Configure Docker Compose
 
-In your application's directory, create a new text file named `docker-compose.yml` with the following content.
+In your application's directory, create a new text file named `compose.yaml` with the following content.
 
 ```yaml
 version: "3.8"
@@ -582,7 +582,7 @@ The exact value doesn't really matter for this example, because you run Cockroac
 
 ### Merging Compose files
 
-The file name `docker-compose.yml` is the default file name which `docker compose` command recognizes if no `-f` flag is provided. This means you can have multiple Docker Compose files if your environment has such requirements. Furthermore, Docker Compose files are... composable (pun intended), so multiple files can be specified on the command line to merge parts of the configuration together. The following list is just a few examples of scenarios where such a feature would be very useful:
+The file name `compose.yaml` is the default file name which `docker compose` command recognizes if no `-f` flag is provided. This means you can have multiple Docker Compose files if your environment has such requirements. Furthermore, Docker Compose files are... composable (pun intended), so multiple files can be specified on the command line to merge parts of the configuration together. The following list is just a few examples of scenarios where such a feature would be very useful:
 
 - Using a bind mount for the source code for local development but not when running the CI tests;
 - Switching between using a pre-built image for the frontend for some API application vs creating a bind mount for source code;
@@ -608,7 +608,7 @@ Before you apply changes made to a Compose configuration file, there is an oppor
 $ docker compose config
 ```
 
-When this command is run, Docker Compose reads the file `docker-compose.yml`, parses it into a data structure in memory, validates where possible, and prints back the reconstruction of that configuration file from its internal representation. If this isn't possible due to errors, Docker prints an error message instead.
+When this command is run, Docker Compose reads the file `compose.yaml`, parses it into a data structure in memory, validates where possible, and prints back the reconstruction of that configuration file from its internal representation. If this isn't possible due to errors, Docker prints an error message instead.
 
 ### Build and run the application using Docker Compose
 

content/guides/java/containerize.md

@@ -204,7 +204,7 @@ services:
 # start the database before your application. The `db-data` volume persists the
 # database data between container restarts. The `db-password` secret is used
 # to set the database password. You must create `db/password.txt` and add
-# a password of your choosing to it before running `docker-compose up`.
+# a password of your choosing to it before running `docker compose up`.
 #     depends_on:
 #       db:
 #         condition: service_healthy

content/guides/nodejs/containerize.md

@@ -141,7 +141,7 @@ services:
 # start the database before your application. The `db-data` volume persists the
 # database data between container restarts. The `db-password` secret is used
 # to set the database password. You must create `db/password.txt` and add
-# a password of your choosing to it before running `docker-compose up`.
+# a password of your choosing to it before running `docker compose up`.
 #     depends_on:
 #       db:
 #         condition: service_healthy

content/guides/nodejs/develop.md

@@ -58,7 +58,7 @@ You can use containers to set up local services, like a database. In this sectio
        # start the database before your application. The `db-data` volume persists the
        # database data between container restarts. The `db-password` secret is used
        # to set the database password. You must create `db/password.txt` and add
-       # a password of your choosing to it before running `docker-compose up`.
+       # a password of your choosing to it before running `docker compose up`.
 
        depends_on:
          db:
@@ -128,7 +128,7 @@ You can use containers to set up local services, like a database. In this sectio
        # start the database before your application. The `db-data` volume persists the
        # database data between container restarts. The `db-password` secret is used
        # to set the database password. You must create `db/password.txt` and add
-       # a password of your choosing to it before running `docker-compose up`.
+       # a password of your choosing to it before running `docker compose up`.
 
        depends_on:
          db:
@@ -188,7 +188,7 @@ You can use containers to set up local services, like a database. In this sectio
        # start the database before your application. The `db-data` volume persists the
        # database data between container restarts. The `db-password` secret is used
        # to set the database password. You must create `db/password.txt` and add
-       # a password of your choosing to it before running `docker-compose up`.
+       # a password of your choosing to it before running `docker compose up`.
 
        depends_on:
          db:

content/includes/hub-limits.md

@@ -3,6 +3,8 @@ title: View billing history
 weight: 40
 description: Discover how to view your billing history in Docker Hub
 keywords: payments, billing, subscription, invoices, renewals, invoice management, billing administration
+aliases:
+    - /billing/core-billing/history/
 ---
 
 In this section, learn how you can view your billing history, manage your invoices, and verify your renewal date. All monthly and annual subscriptions are automatically renewed at the end of the term using the original form of payment.