docs: add Docker installation to READMEs

[yimsk]

Summary

• Add Docker installation section to all READMEs (en, ja, zh-CN, ko)

[claude]

PR Review: docs: add Docker installation to READMEs

This is a clean, straightforward documentation addition. The Docker command is technically correct and aligns well with the existing Dockerfile. A few observations:

Correctness ✓

• The volume mount path /home/claws/.aws correctly matches the claws user home defined in the Dockerfile
• The :ro (read-only) flag on the AWS credentials mount is good security practice
• --rm and -it are the right flags for a TUI application
• The image ghcr.io/clawscli/claws is correctly published via the docker.yml workflow with multi-arch support (amd64 + arm64)

Issues / Suggestions

Minor: Extra blank line in non-English READMEs

README.ja.md, README.ko.md, and README.zh-CN.md each have two blank lines before ### Docker, while README.md has one. This is a small inconsistency worth normalizing.

-
-
 ### Docker

Suggestion: Version-pinned example

Using ghcr.io/clawscli/claws without a tag pulls :latest, which can silently change. For a documentation snippet, consider showing both options or at least noting that users can pin a version:

docker run -it --rm \
  -v ~/.aws:/home/claws/.aws:ro \
  ghcr.io/clawscli/claws:latest   # or pin: ghcr.io/clawscli/claws:v1.2.3

Suggestion: Show how to pass claws flags

The Quick Start section (right below) shows profile/region flags like -p myprofile and -r us-west-2. It may help to include a brief example showing those still work with Docker:

docker run -it --rm \
  -v ~/.aws:/home/claws/.aws:ro \
  ghcr.io/clawscli/claws -p myprofile -r us-west-2

Suggestion: AWS environment variable alternative

Some users authenticate via environment variables rather than ~/.aws. A note or alternative example would make the Docker section complete for all credential setups:

docker run -it --rm \
  -e AWS_ACCESS_KEY_ID \
  -e AWS_SECRET_ACCESS_KEY \
  -e AWS_SESSION_TOKEN \
  ghcr.io/clawscli/claws

Summary

The core change is correct and a welcome addition. The extra blank line issue is a trivial fix. The other suggestions are optional improvements — feel free to leave them for a follow-up PR if you prefer to keep this focused.

[claude]

PR Review: docs: add Docker installation to READMEs

Overall this is a clean, well-structured docs addition. The command is consistent across all four language READMEs, correctly uses ro for the AWS credentials mount, and -it --rm are the right flags for an interactive TUI container. A few observations:

Correctness

The volume mount path /home/claws/.aws correctly matches the Dockerfile's adduser -D -h /home/claws claws / USER claws setup — good catch.

Suggestions

1. No image tag specified

ghcr.io/clawscli/claws        # implicitly pulls :latest

latest is convenient but can silently change between runs. Consider either showing how to pin a version, or at least adding a note:

# pin to a specific release (recommended for reproducibility)
docker run -it --rm \
  -v ~/.aws:/home/claws/.aws:ro \
  ghcr.io/clawscli/claws:v0.x.y

2. Passing CLI arguments

The Quick Start section shows flags like -p, -r, and --read-only, but the Docker example doesn't hint that these work the same way. A one-liner note or example would help:

# Example: specify profile and region
docker run -it --rm \
  -v ~/.aws:/home/claws/.aws:ro \
  ghcr.io/clawscli/claws -p myprofile -r us-west-2

3. Users without a ~/.aws directory

Some users authenticate via environment variables (AWS_ACCESS_KEY_ID, AWS_SESSION_TOKEN, etc.) or rely on EC2/ECS IAM roles. A brief mention of the -e approach as an alternative would improve coverage:

docker run -it --rm \
  -e AWS_ACCESS_KEY_ID \
  -e AWS_SECRET_ACCESS_KEY \
  -e AWS_SESSION_TOKEN \
  ghcr.io/clawscli/claws

Minor

• The section title ### Docker is consistent across all four files. ✓
• Placement (after Go Install, before Quick Start) is logical. ✓
• All four READMEs are updated identically. ✓

None of the above are blockers — the current command works correctly for the common case. The suggestions are enhancements to cover more user scenarios. Happy to approve as-is or with the additions if the maintainers agree they add value.