To live load from MinIo,Error : All access to this bucket has been disabled

I used Live to import data from Minio, but it didn’t work
I’ve set the environment variable




dgraph live -a -z -f minio:// -s minio://


root@server13:/home/user/v21.3.0/dgraph# dgraph live -a -z -f minio:// -s minio://
I0426 14:34:17.806668   35427 init.go:110]

Dgraph version   : v21.03.0
Dgraph codename  : rocket-mod
Dgraph SHA-256   : 7d5902a16e3169b96d9ba8246ffd769c80eba93f9bdff6cfff52a176da7b4ac4
Commit SHA-1     : a77bbe8ae
Commit timestamp : 2021-04-07 21:36:38 +0530
Branch           : heads/v21.03.0
Go version       : go1.16.2
jemalloc enabled : true

For Dgraph official documentation, visit
For discussions about Dgraph     , visit
For fully-managed Dgraph Cloud   , visit

Licensed variously under the Apache Public License 2.0 and Dgraph Community License.
Copyright 2015-2021 Dgraph Labs, Inc.

Running transaction with dgraph endpoint:

Processing schema file "minio://"
E0426 14:34:17.816828   35427 run.go:257] Error while reading file ReadAll: All access to this bucket has been disabled.
2021/04/26 14:34:17 All access to this bucket has been disabled.
Error while reading file

@joaquin can you help?

@lee.chen @MichelDiz For the MinIO service, is it really bound to 3080 port and not the default 9000 port? Is the bucket named minio, with folder path of of data/movie/movie?

I was able to get this working locally using docker-compose.

My steps (running from bash):

## bring up test environment
docker-compose up -d

## using mc command line tool, create a bucket named "movie"
mc alias set local http://localhost:9000 accesskey secretkey
mc mb local/movie

## download files locally
FILES=(21million.schema 21million.rdf.gz)
for FILE in ${FILES[*]}; do 
  curl --silent --location --remote-name $PREFIX/$FILE

## upload files to bucket
mc cp 21million.rdf.gz  21million.schema local/movie

## do live loader from alpha1 
## NOTE: This could could be any container running dgraph v21.03.0
##       on the same netowrk.
docker exec -t alpha1 dgraph live \
  --alpha ${DGRAPH_ALPHA}:9080 \
  --zero ${DGRAPH_ZERO}:7080 \
  --schema minio://minio:9000/movie/21million.schema?secure=false \
  --files minio://minio:9000/movie/21million.rdf.gz?secure=false

My docker-compose.yaml file showing configuration of Dgraph Alpha is the following:

version: "3.5"
    image: dgraph/dgraph:v21.03.0
    command: dgraph zero --my=zero1:5080 --replicas 1 --raft idx=1
    container_name: zero1

    image: dgraph/dgraph:v21.03.0
      MINIO_ACCESS_KEY: accesskey
      MINIO_SECRET_KEY: secretkey
      DGRAPH_ALPHA_SECURITY: whitelist=,,
      - 8080:8080
      - 9080:9080
    command: dgraph alpha --my=alpha1:7080 --zero=zero1:5080
    container_name: alpha1

    image: minio/minio:RELEASE.2021-04-22T15-44-28Z
      MINIO_ACCESS_KEY: accesskey
      MINIO_SECRET_KEY: secretkey
      - 9000:9000
    command: server /data
    container_name: mini

This is my UI once deployed. I noticed that minio web ui adds minio/ to the http path, which is not part of the actually path (as it’s an artifact of their web service only):

1 Like

I didn’t start Minio in docker-compose, so I can confirm that the port is correct

The docker-compose was just for example purposes, to show that the functionality works. Was this useful, are you still stuck?

@lee.chen you are using the web browser URL /minio/ but you cannot use that when you are accessing objects not via the UI. Take out the /minio/ from your URL givien to the live loader.