Giters

supabase / realtime

Broadcast, Presence, and Postgres Changes via WebSockets

Home Page:https://supabase.com/realtime

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

Docker pull: "Retrying after 4s: public.ecr.aws/supabase/realtime:v2.25.50"

Nezteb opened this issue · comments

commented

Bug report

  • I confirm this is a bug with Supabase, not with my own application.
  • I confirm I have searched the Docs, GitHub Discussions, and Discord.

Describe the bug

Lately when I run supabase start, I get errors when pulling the supabase/realtime container image:

> supabase start
v2.25.50: Pulling from supabase/realtime
66dbba0fb1b5: Pull complete 
4166bd72e87a: Pull complete 
5dd8dfaab4d9: Extracting [==================================================>]  864.5kB/864.5kB
07484305c37f: Download complete 
a29e87bf71ee: Download complete 
933c3bd59c23: Download complete 
9614f9b82227: Download complete 
3031aaa00e8d: Download complete 
2faab5f119c5: Download complete 
f54398b16e61: Download complete 
2ffe6f08fe84: Download complete 
0aa8ae17bf21: Download complete 
failed to display json stream: failed to register layer: rename /var/lib/docker/image/overlay2/layerdb/tmp/write-set-3973503769 /var/lib/docker/image/overlay2/layerdb/sha256/8e3d2f17bc8822e0f6b7980858c5e5a0fdb5b26e485bb1f59708f979622e7bd1: file exists
Retrying after 4s: public.ecr.aws/supabase/realtime:v2.25.50

If I run supabase start -x realtime to not start the container, things work fine.

I have tried manually removing the destination file, but that doesn't change anything (even when running supabase stop first).

To Reproduce

Not sure; I'd have to reproduce this in a minimal sample project.

Expected behavior

This used to work fine; I'm not sure what has changed. 🤔

System information

  • OS: macOS 14.4.1
  • Container runtime: OrbStack 1.5.1
  • Version of Node.js: 20.11.0
  • Version of Yarn: 4.1.0
  • Version of supabase-js: 1.153.4

Additional context

I also opened an issue with OrbStack in case it's an issue there: orbstack/orbstack#1123. It seems like the more likely culprit, but it hasn't put out any updates in a little while so I wanted to post here just in case too.