Upon running a repo with supabase in Google's project.idx, i get the following error:
supabase:migrate: StorageUnknownError: fetch failed
supabase:migrate: at /home/user/repo-name/node_modules/.pnpm/@supabase+storage-js@2.5.5/node_modules/@supabase/storage-js/src/lib/fetch.ts:32:12
supabase:migrate: at Generator.next (<anonymous>)
supabase:migrate: at fulfilled (/home/user/jocky/node_modules/.pnpm/@supabase+storage-js@2.5.5/node_modules/@supabase/storage-js/dist/main/lib/fetch.js:5:58) {
supabase:migrate: __isStorageError: true,
supabase:migrate: originalError: TypeError: fetch failed
supabase:migrate: at node:internal/deps/undici/undici:12345:11 {
supabase:migrate: cause: SocketError: other side closed
supabase:migrate: at Socket.onSocketEnd (node:internal/deps/undici/undici:8903:26)
supabase:migrate: at Socket.emit (node:events:530:35)
supabase:migrate: at Socket.emit (node:domain:488:12)
supabase:migrate: at endReadableNT (node:internal/streams/readable:1696:12)
supabase:migrate: at processTicksAndRejections (node:internal/process/task_queues:82:21) {
supabase:migrate: code: 'UND_ERR_SOCKET',
supabase:migrate: socket: [Object]
supabase:migrate: }
supabase:migrate: }
supabase:migrate: }
it seems as when the command 'docker compose -f supabase/docker-compose.yml -p supabase up -d' it continually tries to fire up the port 8000 but not successfully.
Bug report
Describe the bug
Upon running a repo with supabase in Google's project.idx, i get the following error:
it seems as when the command 'docker compose -f supabase/docker-compose.yml -p supabase up -d' it continually tries to fire up the port 8000 but not successfully.
this is my
docker-compose.yml
for reference: