Docker desktop 4.36.0 fails to start with "more than one sd* disk in /sys/block" #14453

chris-riddell35 · 2024-11-28T16:25:12Z

Description

Unable to start docker desktop version 4.36.0; I am consistently seeing the following error:

running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2024-11-28T16:04:44.799442528Z][wsl-bootstrap][F] more than one sd* disk in /sys/block with wwid ending by 57de6aa93848de02790adcb4: /dev/sdb,/dev/sdd"

Reproduce

Start docker desktop

Expected behavior

Docker desktop should start successfully

docker version

Client:
 Version:           27.3.1
 API version:       1.47
 Go version:        go1.22.7
 Git commit:        ce12230
 Built:             Fri Sep 20 11:42:27 2024
 OS/Arch:           windows/amd64
 Context:           desktop-linux

docker info

Client:
 Version:    27.3.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Ask Gordon - Docker Agent (Docker Inc.)
    Version:  v0.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-ai.exe
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.18.0-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.30.3-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.15
    Path:     C:\Program Files\Docker\cli-plugins\docker-desktop.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.15.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
ERROR: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.47/info": context canceled
errors pretty printing info

Diagnostics ID

1AA58D3A-8AF2-493C-AEAF-41A589D2DF25/20241128162112

Additional Info

WSL version info:

wsl --version
WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4460

The text was updated successfully, but these errors were encountered:

MarcelBolten · 2024-11-28T19:55:54Z

Hi,

I'm also observing the same error:

running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2024-11-28T19:48:55.345483430Z][wsl-bootstrap][F] more than one sd* disk in /sys/block with wwid ending by 57de6aa93848de02790adcb4: /dev/sdc,/dev/sde"

docker version

Client:
 Version:           27.3.1
 API version:       1.47
 Go version:        go1.22.7
 Git commit:        ce12230
 Built:             Fri Sep 20 11:42:27 2024
 OS/Arch:           windows/amd64
 Context:           desktop-linux
error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.47/version": open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.

docker info

Client:
 Version:    27.3.1
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  ai: Ask Gordon - Docker Agent (Docker Inc.)
    Version:  v0.1.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-ai.exe
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.18.0-desktop.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-buildx.exe
  compose: Docker Compose (Docker Inc.)
    Version:  v2.30.3-desktop.1
    Path:     C:\Program Files\Docker\cli-plugins\docker-compose.exe
  debug: Get a shell into any image or container (Docker Inc.)
    Version:  0.0.37
    Path:     C:\Program Files\Docker\cli-plugins\docker-debug.exe
  desktop: Docker Desktop commands (Alpha) (Docker Inc.)
    Version:  v0.0.15
    Path:     C:\Program Files\Docker\cli-plugins\docker-desktop.exe
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.2
    Path:     C:\Program Files\Docker\cli-plugins\docker-dev.exe
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.27
    Path:     C:\Program Files\Docker\cli-plugins\docker-extension.exe
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.5
    Path:     C:\Program Files\Docker\cli-plugins\docker-feedback.exe
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.4.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-init.exe
  sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
    Version:  0.6.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-sbom.exe
  scout: Docker Scout (Docker Inc.)
    Version:  v1.15.0
    Path:     C:\Program Files\Docker\cli-plugins\docker-scout.exe

Server:
ERROR: error during connect: Get "http://%2F%2F.%2Fpipe%2FdockerDesktopLinuxEngine/v1.47/info": open //./pipe/dockerDesktopLinuxEngine: The system cannot find the file specified.
errors pretty printing info

Diagnostics ID

ECCA2C28-89D7-4B8B-93C2-DBB853C4B6E2/20241128194210

Additional Info

WSL version info:

WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4460

beegotsy · 2024-11-29T08:34:42Z

For those who need to get Docker working; rollbacking to 4.35.1 (release page) works:

# install pending WSL updates with
wsl.exe --update
# install the previous version of Docker for Windows with:
.\<installer path>.exe install --disable-version-check

You will need to rebuild all images and containers, or at least that's what I did.
For me, the WSL update changed the error from a generic one to more than one sd* disk in /sys/block with wwid ending by ....

This seems a fix to get 4.36.0 working: #14447 (comment)

griesi007 · 2024-11-29T08:59:47Z

same issue for me #14445

rupasix · 2024-11-29T09:13:54Z

I have same issue, screenshot from error:

After that i checked with command "lsblk" if there is sde block and there was none:

lerouxm · 2024-11-29T09:17:47Z

Same issue here with an up to date wsl.
I can confirm that rolling back to previous 3.5.1 fixed the problem for me for now.

dev-mich · 2024-11-29T10:19:28Z

I had the same issue, but completely uninstalling and reinstalling resolved it for me.

bastian-kurz · 2024-11-29T10:52:53Z

I had the same issue. I solved it by going to 'Troubleshoot,' then clicking on 'Clean/Purge Data,' and selecting 'Hyper-V & WSL2.

after that Docker Engine starts again.

andrea-reale · 2024-11-29T11:57:19Z

Hello everyone,

thanks for reporting the problem. Could you please share the output of wsl --list?

From the diagnostics kindly shared by @chris-riddell35 , it looks like WSL2 is in a state where it believes there are two disks with the same identifiers, which makes Docker Desktop boot fail.

Could you please confirm if shutting down WSL after quitting Docker Desktop (wsl.exe --shutdown) helps fixing the issue or not? (Alternative a Windows restart should also be equivalent)

chris-riddell35 · 2024-11-29T13:38:30Z

Hi @andrea-reale ,

I've done several Windows restarts, with the same result each time.

Here's the output of wsl --list:

wsl --list -v
  NAME              STATE           VERSION
* Ubuntu-20.04      Running         2
  Ubuntu            Stopped         1
  Ubuntu-24.04      Stopped         2
  docker-desktop    Stopped         2

andrea-reale · 2024-11-29T13:49:17Z

Hey @chris-riddell35 ,

thanks for your quick response and for confirming. I am having a hard time to try and reproduce the issue.
However, I will be shortly sharing a development build of Docker Desktop with a tentative fix.

I'd sincerely appreciate if you could help us by trying it out and confirm if it addresses the problem or not. If it does, I'll try to get it included in the upcoming 4.37 release.

andrea-reale · 2024-11-29T15:03:00Z

@chris-riddell35, all: as promised here's a development build of Docker Desktop 4.36 that should includes a fix for the issue: installer for windows x86.

Please, let me know if that helps with the more than one sd* disk error discussed in this ticket, and feel free to provide any further feedback (make sure to share diagnostics in case you stumble into different errors).

Note that being a development build, the installer is unsigned and you'll need to tell Windows you trust it, before it will let you run it. You can do so by right-clicking on the file -> Properties -> Unblock.

thomaswiradikusuma · 2024-11-29T15:08:21Z

I had exactly this error as well, right after upgrading. It disappears after few times open-crash-close-open-crash-close-open :)

Cristy94 · 2024-11-29T15:19:35Z

I have the same issue with 4.36.0, it suddenly stopped working.

running engine: waiting for the Docker API: engine linux/wsl failed to run: starting WSL engine: error spotted in wslbootstrap log: "[2024-11-29T15:17:21.165474510Z][wsl-bootstrap][F] more than one sd* disk in /sys/block with wwid ending by 57de6aa93848de02790adcb4: /dev/sdc,/dev/sdd"

wsl --list
Windows Subsystem for Linux Distributions:
docker-desktop (Default)

Cristy94 · 2024-11-29T15:25:50Z

I had the same issue. I solved it by going to 'Troubleshoot,' then clicking on 'Clean/Purge Data,' and selecting 'Hyper-V & WSL2.

after that Docker Engine starts again.

Where did you find "Troubleshoot"?

Nevermind, it's here:

EDIT:

Purging the data works (note that you will lose all containers).

salvorapi · 2024-11-29T15:27:58Z

@chris-riddell35, all: as promised here's a development build of Docker Desktop 4.36 that should includes a fix for the issue: installer for windows x86.

Please, let me know if that helps with the more than one sd* disk error discussed in this ticket, and feel free to provide any further feedback (make sure to share diagnostics in case you stumble into different errors).

Note that being a development build, the installer is unsigned and you'll need to tell Windows you trust it, before it will let you run it. You can do so by right-clicking on the file -> Properties -> Unblock.

it work 👍

chris-riddell35 · 2024-11-29T16:04:37Z

@andrea-reale after installing and restarting, docker desktop is up and running but something is wrong with the wsl2 integration. I see this error message:

Diagnostics ID:
1AA58D3A-8AF2-493C-AEAF-41A589D2DF25/20241129155916

If I run docker from powershell, it's working. I typically use wsl2 and I have all my configurations there so this is still inconvenient, but appears to be workable. Let me know if I can gather more information about the new error.

chris-riddell35 · 2024-11-29T16:23:10Z

@andrea-reale I disabled the WSL integration, re-enabled and restarted Windows and this seems to be working now. I lost all my images when I did that, but I think the system is ok now.

I had also had two wsl2 distros active there, and I disabled one of them. I guess that may have helped fix this issue.

andrea-reale · 2024-11-29T16:29:43Z

Hey @chris-riddell35 , thanks for reporting back your experience.

Glad to hear that the dev build fixed at least the startup issue. And I am sorry about the troubles with the Ubuntu integration. It looks like the previous integration moved to an unhealthy state after the upgrade: glad that disabling it and enabling it again mitigated the problem.

I'll look more into the diagnostics you provided to understand more about why the integration issue started to begin with.

SparkInChief · 2024-11-29T19:48:18Z

@andrea-reale — The dev build resolved the issue for me as well (same error message immediately after upgrading to 4.36.0).

I did not have to reboot (or purge anything), but I did lose all locally cached images and had to rebuild all images and restart containers.

Here's output of wsl --version in case it helps determine what systems the dev build works for (and why it doesn't work on others):

WSL version: 2.3.26.0
Kernel version: 5.15.167.4-1
WSLg version: 1.0.65
MSRDC version: 1.2.5620
Direct3D version: 1.611.1-81528511
DXCore version: 10.0.26100.1-240331-1435.ge-release
Windows version: 10.0.22631.4541

neonima1995 · 2024-11-30T11:57:18Z

Removing Ubuntu from Windows helped me.

theswissguy · 2024-12-01T17:05:02Z

'Troubleshoot,' then clicking on 'Clean/Purge Data,' helped in my case. Docker Desktop starts, but in won't let my sign in. I'm been redirected to https://app.docker.com/auth/ and back to Docker Desktop, but all I get is

WesWedding · 2024-12-02T01:22:21Z

@chris-riddell35, all: as promised here's a development build of Docker Desktop 4.36 that should includes a fix for the issue: installer for windows x86.

Please, let me know if that helps with the more than one sd* disk error discussed in this ticket, and feel free to provide any further feedback (make sure to share diagnostics in case you stumble into different errors).

Note that being a development build, the installer is unsigned and you'll need to tell Windows you trust it, before it will let you run it. You can do so by right-clicking on the file -> Properties -> Unblock.

This development package has addressed the issue for me. I did not attempt to manually purge cached data yet, as mentioned in an earlier post by another user upthread.

xmontero · 2024-12-02T08:46:17Z

Same problem.

Solutions so far?

It seems I could uninstall and re-install an older version. But it seems to loose images and containers. I can't afford that loose.
Development build.

Question: a) "Dev build" means a re-installation of a new version? b) Will I loose any data by doing so? I have production data that I can't loose.

xmontero · 2024-12-02T08:58:17Z

@chris-riddell35, all: as promised here's a development build of Docker Desktop 4.36 that should includes a fix for the issue: installer for windows x86.

Is there any risk of loosing my images, containers, networks and/or volumes by running the installer?

xmontero · 2024-12-02T09:21:19Z

Hey, hey hey hey hey!!!

The installer REMOVED my docker-desktop-data volume!!!!

This means I lost EVERYTHING?!?!?!?!?!?!?

How can this happen without notice!? At least an alert or if you want at least don't using it but "leaving it alone"!!! But... removed ALL MY DATA !?!?!?

xmontero · 2024-12-02T09:39:35Z

Here's the complete sequence I did:

Downloaded the dev-version
Run the installer
After the installer run, I run docker desktop
A black window with many logs appeared and at some point Avast was persistently complaining. I thought as it was a dev version and non-signed maybe that was not good for avast so I disabled avast.
Finally the Desktop Docker GUI appeared and I could see the images, containers, volumes, etc. there inside so it seemed I did not loose anything.
I rebooted the PC to check all was in place.
After rebooting the PC, no images, no containers, no anything...
Doing wsl --list I see Ubuntu-20.04 and docker-desktop but no docker-desktop-data.

May I recover the lost docker-desktop-data from somewhere? I'm happy to copy everything manyally if needed,... but I can't figure out why an software installer should be wiping-out a full virtual disk of data (even if it's data managed by that software).

andrea-reale · 2024-12-02T10:16:33Z

Hi @xmontero,

I am sorry about your issues.
It is expected not to have a docker-desktop-data distribution anymore as there is no longer need of a separate distribution to hold your data. Your data is now stored in <$LOCALAPPDATA>/wsl/disk/docker_data.vhdx. This is not something introduced with the dev build. The expected behaviour is what you saw in your step 5 above.
What is not expected is to lose data after a reboot, of course.

Could you please share a diagnostics bundle and ID, so we can look more to understand what may have happened?

neonima1995 · 2024-12-02T10:23:29Z

@theswissguy @xmontero @andrea-reale @WesWedding
Friends, are you kidding? There is no need to delete data or reinstall anything there. There is a conflict for those who have more than one WSL Linux system installed. docker-desktop is also a Linux distribution, so Ubuntu and docker-desktop conflict with each other. Just need to configure in Docker or uninstall Ubuntu distribution!

xmontero · 2024-12-02T11:27:21Z

Could you please share a diagnostics bundle and ID, so we can look more to understand what may have happened?

Sure! I'll provide everything needed!

Any link or pointer on how to get this data? I'm ready to read already-written articles if needed.

xmontero · 2024-12-02T11:39:17Z

Up to now, from a gitbash in Windows:

xavi@msi-laptop:/c/usr_local/bin/ls all$ find /c/Users/xavi/AppData -iname "*.vhdx"
/c/Users/xavi/AppData/Local/Docker/wsl/disk/docker_data.vhdx
/c/Users/xavi/AppData/Local/Docker/wsl/main/ext4.vhdx
find: ‘/c/Users/xavi/AppData/Local/ElevatedDiagnostics’: Permission denied
find: ‘/c/Users/xavi/AppData/Local/Microsoft/Windows/INetCache/Low/Content.IE5’: Permission denied
/c/Users/xavi/AppData/Local/Packages/CanonicalGroupLimited.Ubuntu20.04onWindows_79rhkp1fndgsc/LocalState/ext4.vhdx
/c/Users/xavi/AppData/Local/Temp/4AC7A3AE-651D-487E-B4DD-07FE052498A2/swap.vhdx
/c/Users/xavi/AppData/Local/Temp/65D2432F-AE03-44BC-BB35-72407D5C52B6/swap.vhdx
find: ‘/c/Users/xavi/AppData/Local/Temp/msdtadmin’: Permission denied

So it seems that /c/Users/xavi/AppData/Local/Docker/wsl/disk/docker_data.vhdx exists.

I would now understand if it contains the "old data" (I hope!) or it's a brand new empty docker_data created by the installer. Should I try to "mount it manually" to inspect? Or better I don't touch anything?

xmontero · 2024-12-02T11:42:21Z

Any link or pointer on how to get this data? I'm ready to read already-written articles if needed.

I'm going to carefully read this https://docs.docker.com/desktop/troubleshoot-and-support/troubleshoot/

If it's not what you need please tell me. Otherwise I'll try to "manually run the diagnose tool" (I'm not confident on launching the docker desktop again, I want to minimize chances of smashing any data).

xmontero · 2024-12-02T11:57:47Z

Could you please share a diagnostics bundle and ID, so we can look more to understand what may have happened?

Here it is:
Diagnostics ID: BB5FCCBA-A57A-422E-A449-A09F8402C9FD/20241202115602 (uploaded)

Is this what you need? Do you need anything else?

andrea-reale · 2024-12-02T16:52:57Z

@xmontero thanks for uploading the diagnostics. I went through the logs and I did not find anything suspicious. Docker Desktop does not have any code (except the factory reset and manual uninstall of course) that deletes your data, so I keep being confident your data is not lost.

Because this is getting a bit off topic for the issue at hand (the more than one sd* disk in /sys/block error - which appears so far to be mitigated by the dev build), would you mind opening another issue so I can try to provide more help for you there tomorrow, please?

xmontero · 2024-12-02T19:29:20Z

would you mind opening another issue so I can try to provide more help for you there tomorrow, please?

Created "Lost data after a docker upgrade" #14461

mattschlosser · 2024-12-02T22:30:24Z

I'm getting the same error:

Diagnostics ID:
EB6FEC5B-2454-48F2-BE6A-B735489D72A4/20241202222120

I can usually get docker to start by doing wsl --shutdwwn and then restarting Docker Desktop, and everything is fine.

Version 4.36.0

maxippacheco · 2024-12-03T00:48:55Z

@chris-riddell35, all: as promised here's a development build of Docker Desktop 4.36 that should includes a fix for the issue: installer for windows x86.

Please, let me know if that helps with the more than one sd* disk error discussed in this ticket, and feel free to provide any further feedback (make sure to share diagnostics in case you stumble into different errors).

Note that being a development build, the installer is unsigned and you'll need to tell Windows you trust it, before it will let you run it. You can do so by right-clicking on the file -> Properties -> Unblock.

It worked for me, you literally saved me LOL

ginocampra · 2024-12-03T02:07:18Z

Thanks guys, it worked great for me too

drewtech · 2024-12-03T03:11:11Z

I'm getting the same error:

Diagnostics ID: EB6FEC5B-2454-48F2-BE6A-B735489D72A4/20241202222120

I can usually get docker to start by doing wsl --shutdwwn and then restarting Docker Desktop, and everything is fine.

Version 4.36.0

running wsl --shutdown and starting docker worked for me too - thanks!

ffes · 2024-12-03T09:26:26Z

Same problem when I already have an active WSL session. When I close that session, run wsl --shutdown Docker Desktop works as expected.

BobDankert · 2024-12-03T20:03:36Z

I also had this issue. Running wsl --shutdown first, then starting docker, then starting other wsl images (Ubuntu - started by just running wsl) after docker was running worked for me. I didn't try the dev build, as I'd rather wait for a new update to be published. Verified the state of WSL images using wsl --list -v as suggested above.

CCadere · 2024-12-04T10:51:52Z

@chris-riddell35, all: as promised here's a development build of Docker Desktop 4.36 that should includes a fix for the issue: installer for windows x86.

Please, let me know if that helps with the more than one sd* disk error discussed in this ticket, and feel free to provide any further feedback (make sure to share diagnostics in case you stumble into different errors).

Note that being a development build, the installer is unsigned and you'll need to tell Windows you trust it, before it will let you run it. You can do so by right-clicking on the file -> Properties -> Unblock.

OMG, thank you for this! Back to work now.

qurm · 2024-12-04T13:17:47Z

I had the above "more than one.." issue today, after allowing Docker Desktop to update itself to 4.36.0. I am running Win 10. Based on a comment above, I restarted and updated WSL as below.
After doing this, Docker Desktop started up fine, with no errors. I did not need to rollback.

PS C:\WINDOWS\system32> wsl --update
Checking for updates.
Updating Windows Subsystem for Linux to version: 2.3.26.
PS C:\WINDOWS\system32> wsl --list
Windows Subsystem for Linux Distributions:
Ubuntu (Default)
docker-desktop-data
PS C:\WINDOWS\system32>

chris-riddell35 added the needs-triage label Nov 28, 2024

docker-robot bot added the version/4.36.0 label Nov 28, 2024

andrea-reale added kind/bug status/2-in-progress area/WSL2 and removed needs-triage labels Nov 29, 2024

andrea-reale self-assigned this Nov 29, 2024

andrea-reale mentioned this issue Dec 2, 2024

Docker failed to start - Issue : 'An unexcepted error occured' #14459

Closed

henixnet mentioned this issue Dec 2, 2024

engine linux/wsl failed to run #14445

Closed

xmontero mentioned this issue Dec 2, 2024

Lost data after a docker upgrade #14461

Open

Docker desktop 4.36.0 fails to start with "more than one sd* disk in /sys/block" #14453

Docker desktop 4.36.0 fails to start with "more than one sd* disk in /sys/block" #14453

Comments

chris-riddell35 commented Nov 28, 2024

Description

Reproduce

Expected behavior

docker version

docker info

Diagnostics ID

Additional Info

MarcelBolten commented Nov 28, 2024

docker version

docker info

Diagnostics ID

Additional Info

beegotsy commented Nov 29, 2024 • edited Loading

griesi007 commented Nov 29, 2024

rupasix commented Nov 29, 2024

lerouxm commented Nov 29, 2024

dev-mich commented Nov 29, 2024

bastian-kurz commented Nov 29, 2024

andrea-reale commented Nov 29, 2024

chris-riddell35 commented Nov 29, 2024

andrea-reale commented Nov 29, 2024

andrea-reale commented Nov 29, 2024 • edited Loading

thomaswiradikusuma commented Nov 29, 2024

Cristy94 commented Nov 29, 2024

Cristy94 commented Nov 29, 2024 • edited Loading

salvorapi commented Nov 29, 2024

chris-riddell35 commented Nov 29, 2024

chris-riddell35 commented Nov 29, 2024

andrea-reale commented Nov 29, 2024 • edited Loading

SparkInChief commented Nov 29, 2024

neonima1995 commented Nov 30, 2024

theswissguy commented Dec 1, 2024

WesWedding commented Dec 2, 2024

xmontero commented Dec 2, 2024

xmontero commented Dec 2, 2024

xmontero commented Dec 2, 2024 • edited Loading

xmontero commented Dec 2, 2024

andrea-reale commented Dec 2, 2024

neonima1995 commented Dec 2, 2024

xmontero commented Dec 2, 2024

xmontero commented Dec 2, 2024

xmontero commented Dec 2, 2024

xmontero commented Dec 2, 2024

andrea-reale commented Dec 2, 2024

xmontero commented Dec 2, 2024

mattschlosser commented Dec 2, 2024 • edited Loading

maxippacheco commented Dec 3, 2024

ginocampra commented Dec 3, 2024

drewtech commented Dec 3, 2024

ffes commented Dec 3, 2024

BobDankert commented Dec 3, 2024

CCadere commented Dec 4, 2024

qurm commented Dec 4, 2024

beegotsy commented Nov 29, 2024 •

edited

Loading

andrea-reale commented Nov 29, 2024 •

edited

Loading

Cristy94 commented Nov 29, 2024 •

edited

Loading

andrea-reale commented Nov 29, 2024 •

edited

Loading

xmontero commented Dec 2, 2024 •

edited

Loading

mattschlosser commented Dec 2, 2024 •

edited

Loading