How to use minio with pocketbase?

[pocketbase]

How to use minio with pocketbase?

[gedw99]

I was working on this today and was planning to make a makefile to make it easy to run minio with Pocketbase locally. Of course also without.

I was also planning to integrate s5cmd . https://github.com/peak/s5cmd . It supports file based and s3 based file operations.

[Lex-2008]

Actually, you don't even need to install minio - they provide a "playground" minio instance at play.min.io:9000, access_key is Q3AM3UQ867SPQQA43P2F, secret_key is zuf+tfteSlswRu7BJ86wekitnifILbZam1KYY3TG.

[ganigeorgiev]

@Lex-2008 I haven't tested with Minio (only DO and Vultr S3 offerings) but I suspect that it is some access control policy misconfiguration or similar. I'll change the endpoint to allow URIs and will update the dev error reporting to include the filesystem errors too.

[Lex-2008]

Thanks! Indeed it might be some issue on my side, since @gedw99 seems to have them running together.

@gedw99: please let me know when you have something, I'll be happy to look at it!

No rush, though.

[gedw99]

Yep will let you all know how it goes.
Thanks for the tips. Supporting every possible s3 out there is a PITA :)

[Lex-2008]

Thanks @ganigeorgiev for implementing plain URL and error logging! I moved a bit closer to solution, but it still doesn't work for me :)

My findings, if anyone finds them useful:

It looks like pocketbase unconditionally prepends bucket name to endpoint and tries to upload file to http://test.127.0.0.1:9000/ (at this point, DNS resolution fails). If I change endpoint to hostname and add it to /etc/hosts - then pocketbase talks to minio, but still unsuccessfully.

Comparing minio "trace" logs generated by pocketbase and s3cmd uploads, it looks like s3cmd first executes s3.GetBucketLocation and then uses hostname without bucketname (i.e. plain localhost - probably as instructed by minio), while pocketbase always prepends bucketname to hostname (i.e. connects to test.localhost) - what confuses minio.

So it looks like minio is not-s3-enough for AWS library used by pocketbase :)

The option S3ForcePathStyle can be related:
https://github.com/aws/aws-sdk-go/blob/main/aws/config.go#L118
but I don't want to push @ganigeorgiev to work on this too much :) especially since AWS themselves deprecated it.

Also, if there's still an option, probably this can be converted to a discussion, since it's not an issue with pocketbase, but actually more like a usage question.