Add MinIO Docker Compose Service #173

NBZ4live · 2021-11-07T17:35:31Z

The New Solution/Problem/Issue/Bug:

This recipe adds a MinIO container to a project.

MinIO is a S3 compatible object-storage.
It can be used, to run an S3 instance locally, in case the hosted S3 is not reachable (like developing while offline)

Manual Testing Instructions:

Follow the instructions from docker-compose-services/minio/README.md.
Expected result:

A working MinIO instance is available in the project.
The object browser is available at https://<projectname>.ddev.site:9000.
All files uploaded through the object browser can be listed with ddev exec -s minio ls -al /data/default

rfay · 2021-11-08T01:51:39Z

Thanks!

rfay

Thanks so much for this contribution! @truls1502 was also working on this at some point, so requesting his review here.

I wasn't able to get this working, from the host browser the http URL says:

$ curl http://d9.ddev.site:9000
<html>
<head><title>400 The plain HTTP request was sent to HTTPS port</title></head>
<body>
<center><h1>400 Bad Request</h1></center>
<center>The plain HTTP request was sent to HTTPS port</center>
<hr><center>nginx/1.20.1</center>
</body>
</html>

And the https port gets a 400 error:

$ curl  https://d9.ddev.site:9000
<?xml version="1.0" encoding="UTF-8"?>
<Error><Code>AccessDenied</Code><Message>Access Denied.</Message><Resource>/</Resource><RequestId>16BF76401B7CA5EB</RequestId><HostId>e3483c39-1c6f-4b72-bcbc-5fe39a3bac71</HostId></Error>

I imagine that's just because I don't know how to provide credentials?

rfay · 2021-12-10T17:11:14Z

docker-compose-services/minio/README.md

+The server is configured through the environment variables in `docker-compose.minio.yaml`
+Default credentials (for API and  object browser):
+* MINIO_ACCESS_KEY=minio
+* MINIO_SECRET_KEY=minio123


I wonder if these would be better to put in config.yaml these days, rather than having people edit the docker-compose.minio.yaml.

rfay · 2021-12-10T17:12:12Z

docker-compose-services/minio/README.md

+* Start (or restart) DDEV to have the service initialized: `ddev start`
+
+## Connection
+* MinIO is available at `ddev-<projectname>-minio:9000` **inside the containers** and at `https://<projectname>.ddev.site:9000` **outside the containers**


Please figure out how to move this to a port other than 9000. 9000 is always such a terrible thing, spurring fights between xdebug and php-fpm... and even minio!!!!

rfay · 2021-12-10T17:28:33Z

docker-compose-services/minio/docker-compose.minio.yaml

+    build:
+      context: './minio-build'
+    restart: always
+    ports:


Please use expose: here instead of ports:. That will make it not create a bind point on the host, which is unneeded.

Suggested change

ports:

expose:

rfay · 2022-01-15T21:26:18Z

Looking forward to getting this in @NBZ4live and thanks for the contribution. Please just pull the suggested commits and rebase and respond to other comments and we can move forward.

smustgrave · 2022-06-17T20:03:22Z

Tried following the steps but unfortunately doesn't seem to be working. Do you know if this should work with the m1 chips?

smustgrave · 2022-06-17T20:04:34Z

https://drupal9-ddev.ddev.site:9000/ redirects to http://drupal9-ddev.ddev.site:39085/ and throws a connection refused error

When I change the port from 9000 to 9005 and try to visit the url I get

502: Unresponsive/broken ddev back-end site.
This is the ddev-router container: The back-end webserver at the URL you specified is not responding. You may want to use "ddev restart" to restart the site.

smustgrave · 2022-06-17T21:20:50Z

Okay finally got it working

`version: '3.6'
services:
minio:
container_name: ddev-${DDEV_SITENAME}-minio
build:
context: './minio-build'
restart: always
ports:
- "9010"
labels:
com.ddev.site-name: ${DDEV_SITENAME}
com.ddev.approot: $DDEV_APPROOT
environment:
- VIRTUAL_HOST=$DDEV_HOSTNAME
- HTTP_EXPOSE=9011:9010
- HTTPS_EXPOSE=9010:9010
- MINIO_ROOT_USER=minio
- MINIO_ROOT_PASSWORD=minio123
command: server /data --console-address :9010
volumes:
- type: "volume"
source: minio
target: "/data"
volume:
nocopy: true
- type: "bind"
source: "."
target: "/mnt/ddev_config"
web:
links:
- minio:$DDEV_HOSTNAME

volumes:
minio:
name: "${DDEV_SITENAME}-minio"
`

rfay · 2022-06-21T18:56:52Z

@mglaman points out that he has minio going on https://github.com/bluehorndigital/mojo

zaifastafa · 2022-11-11T12:34:06Z

Hi @rfay any info on this? I was hoping to have a service as well for local development.

if I use this file

version: '3.6'
services:
  storage:
    container_name: ddev-${DDEV_SITENAME}-minio
    image: minio/minio
    command: 'server /data --console-address ":9001" --address ":8080" '
    volumes:
      - storage:/data
    environment:
      - LOG_LEVEL=trace
      - MINIO_ROOT_USER=minioadmin
      - MINIO_ROOT_PASSWORD=minioadmin
      - MINIO_DOMAIN=storage
      # DDEV configurations to expose MinIO over the network.
      - VIRTUAL_HOST=$DDEV_HOSTNAME
      - HTTP_EXPOSE=8081:8080
      - HTTPS_EXPOSE=8080:8080
    expose:
      - '8080'
      - '9001'
    labels:
      # These labels ensure this service is discoverable by ddev
      com.ddev.site-name: ${DDEV_SITENAME}
      com.ddev.approot: $DDEV_APPROOT
    networks:
      default:
        aliases:
          - mojodata.storage
  storage_cli:
    container_name: ddev-${DDEV_SITENAME}-mc
    image: minio/mc
    depends_on:
      - storage
    entrypoint: /bin/bash
    stdin_open: true
    tty: true

  web:
    environment:
      FILESYSTEM_DRIVER: s3
      AWS_ACCESS_KEY_ID: minioadmin
      AWS_SECRET_ACCESS_KEY: minioadmin
      AWS_DEFAULT_REGION: us-east-1
      S3_BUCKET: mojodata
      S3_PROTOCOL: https
      S3_CNAME: ${DDEV_SITENAME}.ddev.site:8080
      S3_ENDPOINT: http://storage:8080
      S3_USE_PATH_STYLE_ENDPOINT: 1
      S3_CNAME_IS_BUCKET: 0
    links:
      - storage:$DDEV_HOSTNAME
volumes:
  storage:

there are issues in starting up the project. Is there any specific thing that I need to adjust in here?

rfay · 2022-11-11T13:31:22Z

@zaifastafa please say what the issues are, and maybe somebody can help you.

It would be great if somebody who uses this would turn it into a ddev add-on.

zaifastafa · 2022-11-11T13:33:01Z

When this file is added and I do ddev restart, the project starts fine but when opening the project it gives 503 ddev error.

rfay · 2022-11-11T13:37:26Z

A 503 normally means you have the wrong docroot or that the docroot has no index.php in it. ddev logs may help you understand the 503.

Please do a standard trivial working project, maybe Drupal9 quickstart or something, and add this, and see if you still have the problem.

seebeen · 2023-08-14T12:16:17Z

Hello,

I've implemented a full DDEV MinIO addon here.
It exposes 9000 only locally, and gets a random port for localhost.

https://github.com/oblakstudio/ddev-minio

Fully tested and it works

timkelty · 2023-12-14T20:31:39Z

FWIW, I have been using @seebeen's ddev-minio and it is working great.

seebeen · 2024-01-18T11:14:18Z

@rfay can we move the ddev-minio to the official namespace?

rfay · 2024-01-18T11:17:13Z

Sure, please open an issue in ddev-minio. I'm in Chile, it may be a while but we'll do it.

Add MinIO Docker Compose Service

fc14bce

rfay suggested changes Dec 10, 2021

View reviewed changes

Uh oh!

Add MinIO Docker Compose Service #173

Are you sure you want to change the base?

Add MinIO Docker Compose Service #173

Uh oh!

Conversation

NBZ4live commented Nov 7, 2021

The New Solution/Problem/Issue/Bug:

Manual Testing Instructions:

Uh oh!

rfay commented Nov 8, 2021

Uh oh!

rfay left a comment

Choose a reason for hiding this comment

Uh oh!

rfay Dec 10, 2021

Choose a reason for hiding this comment

Uh oh!

rfay Dec 10, 2021

Choose a reason for hiding this comment

Uh oh!

rfay Dec 10, 2021

Choose a reason for hiding this comment

Uh oh!

rfay commented Jan 15, 2022

Uh oh!

smustgrave commented Jun 17, 2022

Uh oh!

smustgrave commented Jun 17, 2022

Uh oh!

smustgrave commented Jun 17, 2022

Uh oh!

rfay commented Jun 21, 2022

Uh oh!

zaifastafa commented Nov 11, 2022

Uh oh!

rfay commented Nov 11, 2022

Uh oh!

zaifastafa commented Nov 11, 2022

Uh oh!

rfay commented Nov 11, 2022

Uh oh!

seebeen commented Aug 14, 2023

Uh oh!

timkelty commented Dec 14, 2023

Uh oh!

seebeen commented Jan 18, 2024

Uh oh!

rfay commented Jan 18, 2024

Uh oh!

Uh oh!