Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

can not cache using minio #338

Open
wumuwumu opened this issue Mar 4, 2022 · 2 comments
Open

can not cache using minio #338

wumuwumu opened this issue Mar 4, 2022 · 2 comments

Comments

@wumuwumu
Copy link

wumuwumu commented Mar 4, 2022

When I use minio, I can't find the corresponding address, S3ForcePathStyle always doesn't work。

docker run -d -p 9001:8080 -e AWS_ACCESS_KEY_ID=AK -e AWS_SECRET_KEY=wJal ghcr.io/willnorris/imageproxy -addr 0.0.0.0:8080 -cache s3://zh-east-1/image-cache/images?endpoint=http://192.168.50.11:9328&disableSSL=1&s3ForcePathStyle=1

error:
http://image-cache.192.168.50.11:9228/images/b3ff1785ff8282ded0e94a9ad5007984": dial tcp: lookup image-cache.192.168.50.11 on 223.5.5.5:53: no such host

version: lastest
os: centos8

@ArcherTrister
Copy link

ArcherTrister commented Aug 15, 2022

@wumuwumu
I also encountered, may I ask you to solve it?

image

image

@rayNip
Copy link

rayNip commented Nov 14, 2022

@ArcherTrister

Try replacing s3:// with http://

S3: s3://{region}/{bucket}/{path} s3://s3-us-east-2.amazonaws.com/bucketname/images
Minio: http://{endpoint}/{bucket}/{path} http://minio.dev:9000/bucketname/images

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants