

# When accessing the minio container on a server with an accessible dns, use the following # For localhost access, add the following to your /etc/hosts s3-client: command line tool to generate presigned urls.minio-mc: command line tool to initialize content.

This compose file contains the following containers: Set HOSTNAME, use 'my-minio-localhost-alias' for localhost export HOSTNAME=my-minio-localhost-alias Create localhost host mapping sudo echo "127.0.0.1 my-minio-localhost-alias" > /etc/hosts The localhost solution is essentially the solution described above. I expanded on the solutions in this question to create a solution that is working for me on both a localhost and on a server with an accessible dns. Is there a way to configure Docker / Laravel / Minio to generate urls which are accessible in- and outside of the Docker network? I've already tried to set AWS_ENDPOINT to but then Laravel can't connect to the Minio Server. This works very well but when I generate a url for a file ( Storage::disk('s3')->url('some-file.txt')) obviously I get a url like this which does not work outside of the Docker network. version: '3'Īs you can see, I use minio as AWS S3 compatible storage. I have the following docker-compose.yml to run a local environment for my Laravel App.
