如何在仅安装Docker的宿主机使用容器内的AWS命令？

Absolutely! This is exactly the kind of scenario Docker was built for—letting you run specialized tools without cluttering up your host system. Here's how to pull this off smoothly:

Step 1: Use the official AWS CLI Docker image #

AWS maintains an official pre-built container image with the AWS CLI fully installed and configured. You won't need to build anything custom; just use amazon/aws-cli directly.

Step 2: Mount your host's backup directory to the container #

For the container to access your database backup file, you'll need to bind-mount the host directory where Jenkins stores the backup into the container. This uses Docker's -v (volume) flag.

Step 3: Pass AWS credentials to the container #

The AWS CLI needs valid credentials to interact with your S3 bucket. You have two secure options to provide them:

Option A: Mount your host's AWS credentials file

If you've manually created an AWS credentials file on your host (even without installing the CLI itself), you can mount it into the container's standard credentials path to avoid exposing keys in command logs:

docker run --rm \
  -v /path/to/host/db-backups:/container-backups \
  -v ~/.aws:/root/.aws \
  amazon/aws-cli s3 cp /container-backups/your-backup-file.sql s3://your-bucket-name/backup-target-path/your-backup-file.sql

Option B: Use environment variables

If you don't have a credentials file, you can pass your access key, secret key, and region directly as environment variables. Just ensure this command is stored securely in Jenkins (avoid plain text logs):

docker run --rm \
  -v /path/to/host/db-backups:/container-backups \
  -e AWS_ACCESS_KEY_ID=your-access-key-id \
  -e AWS_SECRET_ACCESS_KEY=your-secret-access-key \
  -e AWS_DEFAULT_REGION=your-aws-region \
  amazon/aws-cli s3 cp /container-backups/your-backup-file.sql s3://your-bucket-name/backup-target-path/your-backup-file.sql

Key flag breakdown #

• --rm: Automatically deletes the container after it finishes running, so you don't leave unused containers cluttering your host.
• -v: Creates a bind mount between the host directory and container directory, making the backup file accessible inside the container.
• -e: Sets environment variables inside the container, which the AWS CLI uses for authentication and region configuration.

Integrate into Jenkins #

Simply add this full Docker command to your Jenkins scheduled task. Jenkins will execute it directly on the host, which spins up the AWS CLI container, runs the upload, then cleans up the container automatically.

Quick checks to avoid issues #

• Verify your AWS credentials have the s3:PutObject permission for the target S3 bucket.
• Double-check the host and container paths to prevent "file not found" errors.
• For more complex AWS operations, you can replace the final s3 cp part with any valid AWS CLI command.

内容的提问来源于stack exchange，提问作者O. Shekriladze