fix: Testcontainers name (#9193)

Also, fix Testcontainers' website. Signed-off-by: Eddú Meléndez <[email protected]>
containers · Oct 4, 2024 · ba11428 · ba11428
1 parent a8a4115
commit ba11428
Show file tree

Hide file tree

Showing 5 changed files with 7 additions and 7 deletions.
diff --git a/website/blog/2023-01-18-release-0.11.md b/website/blog/2023-01-18-release-0.11.md
@@ -51,7 +51,7 @@ Please feel free to submit any feedback you have, we are looking forward to hear
 
 ### Docker compatibility mode [#1047](https://github.com/containers/podman-desktop/pull/1047)
 
-The Docker compatibility mode is a feature that allows to use Podman as a drop-in replacement for Docker. It relies on the Docker socket helper provided with Podman and automatically handle the local setup of Podman path to the Docker socket. Tools like [Testcontainers](https://www.testcontainers.org/) or others are relying on this to communicate to the container engine.
+The Docker compatibility mode is a feature that allows to use Podman as a drop-in replacement for Docker. It relies on the Docker socket helper provided with Podman and automatically handle the local setup of Podman path to the Docker socket. Tools like [Testcontainers](https://www.testcontainers.com/) or others are relying on this to communicate to the container engine.
 
 In this new version of Podman Desktop, we are now providing information to the user about the status of this compatibility mode directly on the dashboard page. The way it works is the following:
 

diff --git a/website/blog/2023-03-24-5-things-to-know-for-a-docker-user.md b/website/blog/2023-03-24-5-things-to-know-for-a-docker-user.md
@@ -43,7 +43,7 @@ On Windows the socket compatibility mode is always enabled by default. On macOS,
 
 That is not an issue because you can enable it by [invoking a CLI tool](https://podman-desktop.io/docs/migrating-from-docker/using-podman-mac-helper) that will setup the compatibility mode.
 
-For example if you use [`TestContainers`](https://www.testcontainers.org/) in your Java project, you can use the compatibility mode to ensure that the tool will use Podman instead of Docker.
+For example if you use [`Testcontainers`](https://www.testcontainers.com/) in your Java project, you can use the compatibility mode to ensure that the tool will use Podman instead of Docker.
 
 ### CLI compatibility
 

diff --git a/website/docs/migrating-from-docker/emulating-docker-cli-with-podman.md b/website/docs/migrating-from-docker/emulating-docker-cli-with-podman.md
@@ -12,7 +12,7 @@ Consider emulating Docker CLI with Podman to migrate transparently to Podman.
 
 - Continue using familiar Docker commands.
 - Take advantage of the benefits of Podman on macOS.
-- Your tools, such as [Maven](https://maven.apache.org/) or [Testcontainers](https://www.testcontainers.org/), communicate with Podman without reconfiguration.
+- Your tools, such as [Maven](https://maven.apache.org/) or [Testcontainers](https://www.testcontainers.com/), communicate with Podman without reconfiguration.
 
 #### Prerequisites
 

diff --git a/website/docs/migrating-from-docker/using-podman-mac-helper.md b/website/docs/migrating-from-docker/using-podman-mac-helper.md
@@ -12,7 +12,7 @@ Consider using `podman-mac-helper` to migrate transparently to Podman on macOS.
 
 - Continue using familiar Docker commands.
 - Take advantage of the benefits of Podman on macOS.
-- Your tools, such as [Maven](https://maven.apache.org/) or [Testcontainers](https://www.testcontainers.org/), communicate with Podman without reconfiguration.
+- Your tools, such as [Maven](https://maven.apache.org/) or [Testcontainers](https://www.testcontainers.com/), communicate with Podman without reconfiguration.
 
 The `podman-mac-helper` tool provides a compatibility layer that allows you to use most Docker commands with Podman on macOS.
 The service redirects `/var/run/docker` to the fixed user-assigned UNIX socket location.
@@ -55,7 +55,7 @@ The service redirects `/var/run/docker` to the fixed user-assigned UNIX socket l
    $ curl -s --unix-socket /var/run/docker.sock "http://v1.41/info"  | jq -r .ServerVersion
    ```
 
-1. Your tools communicating to the Docker socket, such as [Maven](https://maven.apache.org/) or [Testcontainers](https://www.testcontainers.org/), communicate with Podman without reconfiguration.
+1. Your tools communicating to the Docker socket, such as [Maven](https://maven.apache.org/) or [Testcontainers](https://www.testcontainers.com/), communicate with Podman without reconfiguration.
 
 1. (Optionally, if the `docker` CLI is installed) The docker CLI context is set to the default value `unix:///var/run/docker.sock`:
 

diff --git a/website/docs/migrating-from-docker/using-the-docker_host-environment-variable.md b/website/docs/migrating-from-docker/using-the-docker_host-environment-variable.md
@@ -15,7 +15,7 @@ Consider using the `DOCKER_HOST` environment variable to migrate transparently f
 
 - Continue using familiar Docker commands.
 - Take advantage of the benefits of Podman.
-- Your tools, such as [Gradle](https://gradle.org/) or [Testcontainers](https://www.testcontainers.org/), communicate with Podman without reconfiguration.
+- Your tools, such as [Gradle](https://gradle.org/) or [Testcontainers](https://www.testcontainers.com/), communicate with Podman without reconfiguration.
 
 #### Prerequisites
 
@@ -101,4 +101,4 @@ $ export DOCKER_HOST=unix://<your_podman_socket_location>
 
 #### Verification
 
-- Your tools using the `DOCKER_HOST` environment variable, such as [Gradle](https://gradle.org/) or [Testcontainers](https://www.testcontainers.org/), communicate with Podman without reconfiguration.
+- Your tools using the `DOCKER_HOST` environment variable, such as [Gradle](https://gradle.org/) or [Testcontainers](https://www.testcontainers.com/), communicate with Podman without reconfiguration.