📚 Sync docs from alaudadevops/tektoncd-operator on 008418e262fa3d4198fa49b2e601f08fa861f54a

Source: docs: remove docker in docs (#718)
Author: yzc
Ref: refs/heads/main
Commit: 008418e262fa3d4198fa49b2e601f08fa861f54a

This commit automatically syncs documentation changes from the source-docs repository.

🔗 View source commit: https://github.com/alaudadevops/tektoncd-operator/commit/008418e262fa3d4198fa49b2e601f08fa861f54a
🤖 Synced on 2025-10-31 08:06:45 UTC

Author: edge-katanomi-app2[bot]

.github/SYNC_INFO.md

@@ -1,10 +1,10 @@
 # Documentation Sync Information
 
-- **Last synced**: 2025-10-24 10:07:41 UTC
+- **Last synced**: 2025-10-31 08:06:45 UTC
 - **Source repository**: alaudadevops/tektoncd-operator
-- **Source commit**: [d921020f4508eb6f1f5702573d8c63238527f1e1](https://github.com/alaudadevops/tektoncd-operator/commit/d921020f4508eb6f1f5702573d8c63238527f1e1)
+- **Source commit**: [008418e262fa3d4198fa49b2e601f08fa861f54a](https://github.com/alaudadevops/tektoncd-operator/commit/008418e262fa3d4198fa49b2e601f08fa861f54a)
 - **Triggered by**: edge-katanomi-app2[bot]
-- **Workflow run**: [#89](https://github.com/alaudadevops/tektoncd-operator/actions/runs/18776535041)
+- **Workflow run**: [#90](https://github.com/alaudadevops/tektoncd-operator/actions/runs/18966544073)
 
 ## Files synced:
 - docs/

docs/en/chains/configure/authentication_for_chains.mdx

@@ -27,7 +27,7 @@ To push to an OCI registry, the Chains controller will look for credentials in t
 
 #### Create a Secret based on existing credentials
 
-If you already ran `docker login`, you can copy the credentials stored in config.json into Kubernetes.
+If you already ran `podman login`, you can copy the credentials stored in config.json into Kubernetes.
 
 :::note
 Make sure that any external credentials store, such as the native keychain of the operating system, is not used to store the credentials and the config.json is of the format:

docs/en/development/component-quickstart/index.md

@@ -267,7 +267,7 @@ Ref : <https://github.com/AlaudaDevops/tektoncd-pipeline/blob/main/.tekton/tp-al
 3. **Image Build Phase**
    - Build multiple component images in parallel (e.g., tkn, proxy, webhook, operator)
    - Each image build includes:
-     - Build Docker images
+     - Build OCI images
      - Update image tag in `values.yaml` and `config` directory
 
 4. **Artifact Upload Phase**

docs/en/development/run_e2e.mdx

@@ -13,7 +13,7 @@ Before starting, please ensure your environment meets the following requirements
 
 ### 1. System Requirements
 - Linux or macOS operating system
-- Docker installed and running
+- Podman installed
 - At least 4GB available memory
 - At least 10GB available disk space
 
@@ -23,7 +23,7 @@ Before starting, please ensure your environment meets the following requirements
 - Cluster version: Kubernetes 1.19+
 
 ### 3. Tool Requirements
-- `docker` command-line tool
+- `podman` command-line tool
 - `allure` optional test report reading tool
 
 ## Quick Start
@@ -32,10 +32,10 @@ Before starting, please ensure your environment meets the following requirements
 
 ```bash
 # Check Docker version
-docker version
+podman version
 
 # Pull the E2E test image
-docker pull registry.alauda.cn:60070/devops/tektoncd/e2e/operator/operator-e2e:latest
+podman pull registry.alauda.cn:60070/devops/tektoncd/e2e/operator/operator-e2e:latest
 ```
 
 > **Note**: The test image is built from the Dockerfile located at `.tekton/dockerfiles/operator-e2e.Dockerfile`.
@@ -267,7 +267,7 @@ Each toolchain contains the following common configuration items:
 ### Step 3: Run E2E Tests
 
 ```bash
-docker run --entrypoint /bin/bash -it \
+podman run --entrypoint /bin/bash -it \
   -e TESTING_CONFIG=/tmp/workspace/config.yaml \
   -e KUBECONFIG=/tmp/workspace/config \
   -v ${PWD}/workspace:/tmp/workspace \
@@ -334,7 +334,7 @@ allure open allure-report/
    curl -I registry.alauda.cn:60070
 
    # Configure image registry authentication
-   docker login registry.alauda.cn:60070
+   podman login registry.alauda.cn:60070
    ```
 
 4. **Test Timeout**
@@ -358,7 +358,7 @@ Enable debug mode to get more detailed logs:
 
 ```bash
 # Run tests with debug mode
-docker run --entrypoint /bin/bash -it \
+podman run --entrypoint /bin/bash -it \
   -e TESTING_CONFIG=/tmp/workspace/config.yaml \
   -e KUBECONFIG=/tmp/workspace/config \
   -e DEBUG=true \

docs/en/hub/tutorials/creating-custom-catalog.mdx

@@ -91,10 +91,10 @@ metadata:
     tekton.dev/categories: "Build Tools"
 
     # Searchable tags (comma-separated, no spaces after commas)
-    tekton.dev/tags: "build,docker,container"
+    tekton.dev/tags: "build,podman,container"
 
     # Human-readable display name
-    tekton.dev/displayName: "Docker Build Task"
+    tekton.dev/displayName: "Podman Build Task"
 
     # Supported platforms (optional)
     tekton.dev/platforms: "linux/amd64,linux/arm64"

docs/en/hub/tutorials/writing-tasks.mdx

@@ -53,8 +53,8 @@ metadata:
   annotations:
     tekton.dev/pipelines.minVersion: "0.17.0"  # Minimum Tekton version
     tekton.dev/categories: "Build Tools"       # Hub category
-    tekton.dev/tags: "build,docker,image"     # Hub search tags
-    tekton.dev/displayName: "Build Docker Image"  # Hub display name
+    tekton.dev/tags: "build,podman,image"     # Hub search tags
+    tekton.dev/displayName: "Build Podman Image"  # Hub display name
     tekton.dev/platforms: "linux/amd64,linux/arm64"  # Supported platforms
 ```
 
@@ -102,7 +102,7 @@ metadata:
 
 ### Effective Tagging
 - Use specific, searchable tags
-- Include technology names (`docker`, `kubernetes`, `npm`, etc.)
+- Include technology names (`podman`, `kubernetes`, `npm`, etc.)
 - Add use case tags (ci, cd, build, test, deploy)
 
 ## `Hub` Validation Requirements

docs/en/pipelines/concepts/stepaction_concept.mdx

@@ -170,14 +170,14 @@ spec:
     - name: context
       type: string
       default: "."
-  image: docker
+  image: podman
   env:
     - name: IMAGE_NAME
       value: $(params.image.name)
     - name: IMAGE_TAG
       value: $(params.image.tag)
   script: |
-    docker build -t $IMAGE_NAME:$IMAGE_TAG $(params.context)
+    podman build -t $IMAGE_NAME:$IMAGE_TAG $(params.context)
 ```
 
 ### Results

docs/en/pipelines/how_to/adjust_dockerfile_for_task_compatible_image.mdx

@@ -27,7 +27,7 @@ The following scenarios require referring to the guidance in this document:
 
 Before using this feature, ensure:
 
-- You have a Docker image building environment
+- You have a OCI image building environment
   - You can use the platform's native build pipeline
   - If you need to use community/open-source tools, ensure you have internet access or have prepared offline packages
 - You have a basic understanding of Dockerfile writing
@@ -43,7 +43,7 @@ First, confirm the release version of the base image, as the command for creatin
 
 ```bash
 # Check the release version of the base image
-$ docker run -it --rm ${registry} cat /etc/os-release
+$ podman run -it --rm ${registry} cat /etc/os-release
 
 # Possible outputs
 NAME="Alpine Linux"
@@ -105,13 +105,13 @@ After building, validate whether the image can run correctly:
 
 ```bash
 # Verify user configuration
-$ docker run -it --rm ${registry} id
+$ podman run -it --rm ${registry} id
 
 # Expected output
 uid=65532(nonroot) gid=65532(nonroot) groups=65532(nonroot)
 
 # Verify application permissions
-$ docker run -it --rm ${registry} ls -la /home/nonroot
+$ podman run -it --rm ${registry} ls -la /home/nonroot
 ```
 
 ## Operation Results

docs/en/pipelines/trouble_shooting/custom_image_pod_creation_failed.mdx

@@ -47,7 +47,7 @@ If this issue only appears when using custom images, it is recommended to follow
 
 1. Verify if the image itself has issues:
    ```bash
-   $ docker run -it --rm ${registry} ${cmd}
+   $ podman run -it --rm ${registry} ${cmd}
    ```
 
 2. Check the compatibility of the Task configuration with the image:

docs/en/pipelines/trouble_shooting/custom_images_cannot_be_used_in_the_run-script.mdx

@@ -50,12 +50,12 @@ If this issue occurs only when using the custom image, it is recommended to trou
 
 1. Verify whether there are insufficient permissions with the image when run as the root user:
    ```bash
-   $ docker run -it --rm --user root ${registry} ${cmd}
+   $ podman run -it --rm --user root ${registry} ${cmd}
    ```
 
 2. Check if the application allows user 65532 to access specific directories or files:
    ```bash
-   $ docker run -it --rm --user 65532:65532 ${registry} ${cmd} ls -la /path/to/directory
+   $ podman run -it --rm --user 65532:65532 ${registry} ${cmd} ls -la /path/to/directory
    ```
 
 3. Check the securityContext configuration of the Task: