Chainguard Container for seata-server

Seata is a high-performance, easy-to-use distributed transaction solution designed for microservices architecture.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/seata-server:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

The seata-server image is compatible with the upstream Apache Seata Server image. Like all Chainguard Containers, this image is a minimal, stripped-down design that reduces attack surface.

The image includes the Seata Server application and its runtime dependencies without unnecessary software bloat.

Getting Started

Seata Server can be run directly using Docker:

docker run -d -p 8091:8091 -p 7091:7091 cgr.dev/ORGANIZATION/seata-server:latest

This command starts Seata Server and exposes:

• Port 8091 for the HTTP service
• Port 7091 for the RPC service

To verify the server is running:

docker logs <container-id>

Deployment with Kubernetes

Create a basic Kubernetes deployment for Seata Server:

apiVersion: v1
kind: Service
metadata:
  name: seata-server
  namespace: default
  labels:
    k8s-app: seata-server
spec:
  type: NodePort
  ports:
    - port: 8091
      nodePort: 30091
      protocol: TCP
      name: http
  selector:
    k8s-app: seata-server

---

apiVersion: apps/v1
kind: Deployment
metadata:
  name: seata-server
  namespace: default
  labels:
    k8s-app: seata-server
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s-app: seata-server
  template:
    metadata:
      labels:
        k8s-app: seata-server
    spec:
      containers:
        - name: seata-server
          image: docker.io/seataio/seata-server:latest
          imagePullPolicy: IfNotPresent
          env:
            - name: SEATA_PORT
              value: "8091"
            - name: STORE_MODE
              value: file
          ports:
            - name: http
              containerPort: 8091
              protocol: TCP

Apply the configuration:

kubectl apply -f seata-deployment.yaml

Configuration

Seata Server can be configured through environment variables and configuration files. The most common configuration options include:

Environment Variables

Key environment variables for configuring Seata Server:

• SEATA_IP: The IP address Seata Server binds to (default: 0.0.0.0)
• SEATA_PORT: The port for the HTTP service (default: 8091)
• STORE_MODE: Transaction log storage mode (file, db, redis)
• SERVER_NODE: Server node ID for cluster deployment

Example with custom configuration:

docker run -d \
  -p 8091:8091 \
  -p 7091:7091 \
  -e SEATA_IP=0.0.0.0 \
  -e SEATA_PORT=8091 \
  -e STORE_MODE=file \
  cgr.dev/ORGANIZATION/seata-server:latest

Using Configuration Files

To provide custom configuration files, mount them as volumes:

docker run -d \
  -p 8091:8091 \
  -p 7091:7091 \
  -v $(pwd)/config:/seata-server/resources \
  cgr.dev/ORGANIZATION/seata-server:latest

This approach allows you to customize application.yml and registry.conf files for more advanced configurations including database connections, registry settings, and transaction modes.

Documentation and Resources

• Apache Seata Official Documentation
• Seata GitHub Repository
• Chainguard Academy: Getting Started with Chainguard Containers

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Libraries — contact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.