https://github.com/jareware/s3cmd
Docker-wrapper for the ever-so-useful s3cmd
https://github.com/jareware/s3cmd
Last synced: 5 months ago
JSON representation
Docker-wrapper for the ever-so-useful s3cmd
- Host: GitHub
- URL: https://github.com/jareware/s3cmd
- Owner: jareware
- License: mit
- Created: 2015-07-02T09:46:31.000Z (almost 11 years ago)
- Default Branch: master
- Last Pushed: 2015-07-04T08:32:47.000Z (almost 11 years ago)
- Last Synced: 2025-10-10T17:33:57.153Z (8 months ago)
- Homepage: https://registry.hub.docker.com/u/jareware/s3cmd/
- Size: 129 KB
- Stars: 0
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
Awesome Lists containing this project
README
# jareware/s3cmd
Docker-wrapper for the ever-so-useful `s3cmd`, with proper tags, convenient entrypoint, and two special locations within the container:
* `/config`, from which the `.s3cfg` is looked for by default. Use `-v` to mount your own, secret config over that.
* `/data`, which is the default workdir. Use `-v` to mount any data you wish to operate on there.
## Usage
Running the container without arguments gives you the `--help`:
```
$ docker run jareware/s3cmd
Usage: s3cmd [options] COMMAND [parameters]
...
```
For operations that require authentication, mount your `~/.s3cfg` to the container:
```
$ docker run -v ~/.s3cfg:/config:ro jareware/s3cmd ls
2015-07-24 20:37 s3://my-bucket
2015-12-26 12:49 s3://another-bucket
```
All commands and arguments work as they would on the unwrapped `s3cmd`. Say you have `important.txt` at your current directory, which you'd want to upload to a publicly available location:
```
$ docker run -v ~/.s3cfg:/config:ro -v $(pwd):/data:ro jareware/s3cmd put --acl-public important.txt s3://my-bucket
```
## Versioning
The tags match the wrapped `s3cmd` release.
## License
MIT