Minio: found backend type fs, expected xl or xl-single

Question

I try to upgrade minio version in my docker commpose(previously I used image: minio/minio:RELEASE.2020-06-22T03-12-50Z and it was working ) For now I have following docker-compose service:

version: '3.6'
services:
  minio:
    container_name: minio
    image: minio/minio:RELEASE.2022-11-17T23-20-09Z.fips
    volumes:
      - minio-data:/data
    ports:
      - 9000:9000
    environment:
      - MINIO_ROOT_USER=minio
      - MINIO_ROOT_PASSWORD=minio123
    command: server /data
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
      interval: 30s
      timeout: 20s
      retries: 3

When I try to start(docker-compose up -d) I see the following error in the minio container log:

2022-11-25 11:40:56 ERROR Unable to use the drive /data: Drive /data: found backend type fs, expected xl or xl-single - to migrate to a supported backend visit https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html: Invalid arguments specified

I've googled the following article https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html

But I still don't understand what shoud I change in my compose file to make it working.

gstackoverflow · Answer 1 · 2022-12-01T09:56:47.187

It is not a solution but workaround how to use a fresh version:

  minio:
    container_name: minio
    image: bitnami/minio:2022.11.17-debian-11-r0
    volumes:
      - minio-data:/data
    ports:
      - 9000:9000
      - 9001:9001
    environment:
      - MINIO_ROOT_USER=minio
      - MINIO_ROOT_PASSWORD=minio123
      - MINIO_DEFAULT_BUCKETS=mybucket1,mybucket2
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:9000/minio/health/live"]
      interval: 30s
      timeout: 20s

Ryabchenko Alexander · Accepted Answer · 2022-12-04T11:25:41.617

2

looks like you need migrate data/fs in your volum to be used in new version of minio

so you need to run steps from https://min.io/docs/minio/linux/operations/install-deploy-manage/migrate-fs-gateway.html

In your compose you need to add

volumes:
   minio-data:
      driver: local

edited Dec 04 '22 at 11:25

answered Dec 04 '22 at 10:23

Ryabchenko Alexander

10,057
7
56
88

I've seen this page but I don't need to migrate because I am not interested in historical data. I just want to run new image minio with empty data. – gstackoverflow Dec 04 '22 at 10:58
than create new empty volum – Ryabchenko Alexander Dec 04 '22 at 11:00
if you shure that you don't need old data then you can run (it will remove old volum and than you can start your docker-compose again): docker volume rm minio-data – Ryabchenko Alexander Dec 04 '22 at 11:03
Sasha, I tried to remove all volumes but it didn't help so it is a reason why I've created this topic. Have you tried tio run it locally using my compose file from the topic ? Does it work for you ? – gstackoverflow Dec 04 '22 at 11:15
what says "docker volume ls" ? – Ryabchenko Alexander Dec 04 '22 at 11:22
tried locally => solution in the answer update – Ryabchenko Alexander Dec 04 '22 at 11:26

score 1 · Answer 3 · edited May 10 '23 at 06:55

1

I had the same error. In my mounting folder there was an old version of .minio.sys folder. Once i removed that folder minio started again. I'm only starting a minio docker container for testing which didn't start anymore when upgrading to the latest minio docker image.

Check out hte docs: minio docker container doc

edited May 10 '23 at 06:55

Community

1
1

answered May 04 '23 at 07:57

Herbert

11
3

1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community May 05 '23 at 23:18

Minio: found backend type fs, expected xl or xl-single

3 Answers3