Web UI container exits with code 137 about stable-diffusion-webui-docker

[Arvoreen]

UPDATE: I switched the allocation to 12G -- and it started (and no lock up)

[Arvoreen]

I'm seeing this same issue -- I configured my .wslconfig file to give it 8G

[Pyroglyph]

This also happens when running docker compose --profile hlky up --build

[+] Running 1/1
 - Container webui-docker-hlky-1  Created                                                                          0.1s
Attaching to webui-docker-hlky-1
webui-docker-hlky-1  | + /docker/mount.sh
webui-docker-hlky-1  | Mounted RealESRGAN_x4plus_anime_6B.pth
webui-docker-hlky-1  | Mounted RealESRGAN_x4plus.pth
webui-docker-hlky-1  | Mounted LDSR.ckpt
webui-docker-hlky-1  | Mounted GFPGANv1.3.pth
webui-docker-hlky-1  | + python3 -u scripts/webui.py --outdir /output --ckpt /cache/models/model.ckpt --ldsr-dir /latent-diffusion --inbrowser --optimized-turbo
webui-docker-hlky-1  | Found GFPGAN
webui-docker-hlky-1  | Found RealESRGAN
webui-docker-hlky-1  | Found LDSR
webui-docker-hlky-1  | Loading model from /cache/models/model.ckpt
webui-docker-hlky-1  | Global Step: 470000
webui-docker-hlky-1  | UNet: Running in eps-prediction mode
webui-docker-hlky-1 exited with code 137

[AbdBarho]

@Pyroglyph How much ram do you have? 16 with WSL is known to cause problems. can you try the points mentioned at the end?

https://github.com/AbdBarho/stable-diffusion-webui-docker/wiki/FAQ#other-build-errors-on-windows-thanks-to-suddendevelopment-for-reporting

try them one by one see if it works.

[Pyroglyph]

How much ram do you have?

I've got 16GB (was going to upgrade to 32 soon anyway)

can you try the points mentioned at the end?

I've tried most of them and I don't think the others apply.

• I'm already past that build of Windows
• I'm already on WSL2
• I have updated Docker Desktop (and I assume that updates Docker too?)
• I created a .wslconfig and set the memory to 16GB (although I've never seen it pass 8GB in Task Manager)

It's most likely a memory issue, which I find strange because I can run a local copy of stability-ai/stable-diffusion perfectly fine.

Why would a web UI need to use so much memory?

[AbdBarho]

I have seen it take up to 14GB on my machine. You can try the --lowvram cli arg for auto in docker-compose.yaml, maybe it helps. Also increase wsl memory to all available memory and try again.

[JoeMojoJones]

I've experienced exit error 137 using AUTOMATIC1111-cpu when trying to generate images that are too large.

It appears to be an out-of-memory type error and I've seen it occur as it fills up physical RAM then eats the swap space

[Arvoreen]

So I tried switching to the full 16G I have in my machine, then it locked up (the entire PC) trying to start the auto UI

[github-actions]

This issue is stale because it has been open 14 days with no activity. Remove stale label or comment or this will be closed in 7 days.

[github-actions]

This issue was closed because it has been stalled for 7 days with no activity.