Bug when using storage locally with docker-compose

Bug report

Describe the bug

I’ve been trying to have Supabase running locally in my computer for testing purposes. I’m using the docker-compose file and I managed to have everything up and running. When I try to connect to the DB everything seems to be working fine, but when I try to use the storage module to upload/retrieve a picture I get the following error:

The file system does not support extended attributes or has the feature disabled

To Reproduce

Steps to reproduce the behavior, please provide code snippets or a repository:

1. Use the docker-compose file to launch Supabase locally
2. Create a bucket in the storage DB (I did this with pgadmin4)
3. Try to upload a picture to the storage with the JS client:

  await client.storage.from(bucket).upload(key, blob, {
    contentType: blob.type,
    upsert: false,
    cacheControl: "public, max-age=31536000, immutable",
  });

Expected behavior

The upload works without getting errors

Screenshots

System information

• OS: macOS Big Sur (11.6)
• Browser: Chrome (95.0.4638.69) and Brave (1.31.87)
• Version of supabase-js: 1.21.0
• Version of Node.js: 14.15.4

[nacho-carnicero]

Ok thanks, for the answer, let me know if you want me to add a PR for documenting this

[soedirgo]

@nacho-carnicero yes this is a macOS-specific Docker limitation - we could document this somewhere. Right now you’d need to use S3-like backend for this to work.