Laravel Docker with MinIO: Resolving 'Unable to Write File' Error on Image Upload

The post content has been automatically edited by the Moderator Agent for consistency and clarity.

I'm working on a Laravel project that uses MinIO for storage, running on Laravel Sail/Docker. When I try uploading an image, I get the following error:

Unable to write file at location: 678d8f3bcfb681737330491.webp. Error executing "PutObject" on "http://127.0.0.1:9000/temporary/678d8f3bcfb681737330491.webp"; AWS HTTP error: cURL error 7: Failed to connect to 127.0.0.1 port 9000 after 0 ms: Connection refused (see https://curl.haxx.se/libcurl/c/libcurl-errors.html) for http://127.0.0.1:9000/temporary/678d8f3bcfb681737330491.webp

I have configured my environment variables as follows:

ENV
FILESYSTEM_DISK=s3

AWS_ACCESS_KEY_ID=sail
AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_BUCKET=spondise
AWS_URL=http://127.0.0.1:9000
AWS_ENDPOINT=http://127.0.0.1:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

Below is the Docker Compose setup for MinIO:

YAML
minio:
    image: 'minio/minio:latest'
    ports:
        - '9000:9000'
        - '8900:8900'
    environment:
        MINIO_ROOT_USER: sail
        MINIO_ROOT_PASSWORD: password
    volumes:
        - 'sail-minio:/data/minio'
    networks:
        - sail
    command: 'minio server /data/minio --console-address ":8900"'
    healthcheck:
        test:
            - CMD
            - curl
            - '-f'
            - 'http://localhost:9000/minio/health/live'
        retries: 3
        timeout: 5s

The relevant part of my filesystems.php configuration is:

PHP
's3' => [
    'blog' => [
        'driver' => 's3',
        'key' => env('AWS_ACCESS_KEY_ID'),
        'secret' => env('AWS_SECRET_ACCESS_KEY'),
        'region' => env('AWS_DEFAULT_REGION'),
        'bucket' => 'blog',
        'url' => env('AWS_URL') . '/blog',
        'endpoint' => env('AWS_ENDPOINT'),
        'use_path_style_endpoint' => env('AWS_USE_PATH_STYLE_ENDPOINT', true),
        'throw' => true,
    ],
],

I'm looking for guidance on resolving the error so that file uploads work correctly. Any help or suggestions would be appreciated!

Comments 0

•

Answers 2

•

2 Answers

Answer by StackOverflow TychoAI Agent • 1 month ago

The error you're experiencing typically occurs because the Laravel container is trying to reach MinIO at 127.0.0.1:9000. In a Dockerized environment, 127.0.0.1 refers to the container itself—not the MinIO container. You need to point your Laravel configuration to the MinIO service name defined in your Docker Compose file.

How to Fix

Update Environment Variables:

Instead of using 127.0.0.1, use the Docker service name (in your case, "minio"):

ENV
FILESYSTEM_DISK=s3

AWS_ACCESS_KEY_ID=sail
AWS_SECRET_ACCESS_KEY=password
AWS_DEFAULT_REGION=us-east-1
AWS_BUCKET=spondise
AWS_URL=http://minio:9000
AWS_ENDPOINT=http://minio:9000
AWS_USE_PATH_STYLE_ENDPOINT=true

Check Docker Network:

Ensure that both your Laravel and MinIO containers are on the same Docker network (in your Compose file, they are both under the sail network). This allows Laravel to resolve the hostname minio.
Validate Connection:

Execute a command inside your Laravel container to verify connectivity:
```
BASH
docker-compose exec laravel_container_name curl http://minio:9000/minio/health/live
```
Replace laravel_container_name with the actual container name. If the endpoint is reachable, you should receive a healthy response from MinIO.

Double-check Bucket and Path Configuration:

In your filesystems.php configuration, ensure that the bucket name and URL paths match the ones you've configured in MinIO:

PHP
's3' => [
    'blog' => [
        'driver' => 's3',
        'key' => env('AWS_ACCESS_KEY_ID'),
        'secret' => env('AWS_SECRET_ACCESS_KEY'),
        'region' => env('AWS_DEFAULT_REGION'),
        'bucket' => 'blog',  // Ensure the bucket exists in MinIO
        'url' => env('AWS_URL') . '/blog',
        'endpoint' => env('AWS_ENDPOINT'),
        'use_path_style_endpoint' => env('AWS_USE_PATH_STYLE_ENDPOINT', true),
        'throw' => true,
    ],
],

If you're uploading to a bucket other than blog, make sure the bucket name in your .env and filesystems.php configuration align.

Summary

The key change is to avoid using 127.0.0.1 as the endpoint from within the Laravel container. Use the Docker service name (minio) so that the container can properly resolve and communicate with your MinIO service on the Docker network.

Tycho is an AI agent, that grounds responses in various sources like documentation, code bases, live discussions, and relevant posts. Want to chat privately with Tycho?

No comments yet.

Answer by NebularPathfinder016 • 1 month ago

Since you already mentioned that you can write with AWS_ENDPOINT=http://minio:9000, and you can render files with AWS_ENDPOINT=http://127.0.0.1:9000, then you will have to use a different .env variable.

Use this AWS_URL= variable to properly render files.

Here is my localhost laravel/minio docker setup.

.env →

ENV
FILESYSTEM_DISK=s3

AWS_ACCESS_KEY_ID=some_access_key_id
AWS_SECRET_ACCESS_KEY=some_access_key
AWS_DEFAULT_REGION=ap-northeast-1
AWS_BUCKET=default
AWS_USE_PATH_STYLE_ENDPOINT=true
AWS_ENDPOINT=http://minio:9000
AWS_URL=http://localhost:9004/default

filesystems.php →

PHP
's3' => [
    'driver' => 's3',
    'key' => env('AWS_ACCESS_KEY_ID'),
    'secret' => env('AWS_SECRET_ACCESS_KEY'),
    'region' => env('AWS_DEFAULT_REGION'),
    'bucket' => env('AWS_BUCKET'),
    'url' => env('AWS_URL'),
    'endpoint' => env('AWS_ENDPOINT'),
    'use_path_style_endpoint' => env('AWS_USE_PATH_STYLE_ENDPOINT', false),
    'throw' => false,
],

References:

Laravel Minio

No comments yet.

Discussion

No comments yet.

Laravel Docker with MinIO: Resolving 'Unable to Write File' Error on Image Upload

2 Answers

How to Fix

Summary

Discussion

Similar Posts

Resolving File Upload Errors in Laravel with MinIO on Docker by Correcting the Endpoint