Docker compose #192

Closed
opened 2026-01-19 18:29:21 +00:00 by michael · 1 comment
Owner

Originally created by @splifter on GitHub.

Hey everyone,

i've tried to run transfer.sh via docker-compose:

transfer:
container_name: transfer
image: dutchcoders/transfer.sh
environment:
- basedir=/tmp/
- provider=S3
- s3-endpoint=https://minio.domain.tld
- bucket=transfer.sh
- aws-access-key=SUPERSECUREKEY
- aws-secret-key=SUPERSECT
- listener=1337

but i alway get:
panic: Provider not set or invalid.

Any suggestions on how to fix this?

Ty!

Originally created by @splifter on GitHub. Hey everyone, i've tried to run transfer.sh via docker-compose: transfer: container_name: transfer image: dutchcoders/transfer.sh environment: - basedir=/tmp/ - provider=S3 - s3-endpoint=https://minio.domain.tld - bucket=transfer.sh - aws-access-key=SUPERSECUREKEY - aws-secret-key=SUPERSECT - listener=1337 but i alway get: `panic: Provider not set or invalid.` Any suggestions on how to fix this? Ty!
Author
Owner

@splifter commented on GitHub:

fixed it with using the command option within the docker-compose file:

command: --basedir /tmp/ --provider s3 --s3-endpoint https://minio.domain.tld --bucket transfer.sh --aws-access-key SUPERSECUREKEY--aws-secret-key SUPERSECT--listener 1337

@splifter commented on GitHub: fixed it with using the command option within the docker-compose file: command: --basedir /tmp/ --provider s3 --s3-endpoint https://minio.domain.tld --bucket transfer.sh --aws-access-key SUPERSECUREKEY--aws-secret-key SUPERSECT--listener 1337
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: dutchcoders/transfer.sh#192