skip to Main Content

We are running Minio in an unintended Docker-compose for testing in our team setups. Means 100 deployments per day and we need to get the secret/access keys somehow. But outside manual via the web console, I cannot find how to do this using the ROOT user we sat in Docker-compose at startup.

There seems only ways to do this using secret/access AFTER you create them in the web console.

The command;

  mc admin user add local ${AWS_ACCESS_KEY_ID} ${AWS_SECRET_ACCESS_KEY}

does not work because I cannot authenticate with a root user/pass (well, I don’t know how to) and the docs only talk about setting your access to your private/access key, but after deployment, I don’t have any yet (which is the point of the question).

2

Answers


  1. Chosen as BEST ANSWER

    With some type of strange naming, the settings you put inside the docker configuration MINIO_ROOT_USER & MINIO_ROOT_PASSWORD which I did, actually are the same as the ACCESS KEY and SECRET. I did not try more because of the naming that differed, so I assumed they are other things.

    I did try this before but it did not work, however it does work. So @siddartha was partially right, but it did not explain that it's exactly the same thing and must work.


  2. I think we can pass the credentials to the docker-compose.yaml file to create the username and password

    version: '3'
    
    services:
      minio:
        image: minio/minio
        ports:
          - "9000:9000"
          - "9001:9001"
        environment:
          MINIO_ROOT_USER: admin
          MINIO_ROOT_PASSWORD: admin
        command: server --console-address ":9001" /data
    volumes:
      minio_storage: {}
    
    Login or Signup to reply.
Please signup or login to give your own answer.
Back To Top
Search