mirror of
https://github.com/open-webui/open-webui.git
synced 2026-05-06 02:48:13 -05:00
infra: Docker images with version tags not being published because of failing builds #1104
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @DavidZidar on GitHub (Jun 2, 2024).
Bug Report
Description
Bug Summary:
I tried pulling
ghcr.io/open-webui/open-webui:0.2.0but it doesn't exist and neither does v0.2.1 because these builds are failing with the errorERROR: registry cache exporter requires refwhendocker buildx buildis being run.Logs and Screenshots
v0.2.0
https://github.com/open-webui/open-webui/actions/runs/9335788157
v0.2.1 (same error)
https://github.com/open-webui/open-webui/actions/runs/9341217307
Installation Method
Docker
Additional Information
The command line in the logs does indeed seem to be missing the ref value because two of the command line args look like this.
--cache-from type=registry,ref= --cache-to type=registry,ref=,mode=max@DavidZidar commented on GitHub (Jun 2, 2024):
Immediately after submitting this issue I noticed PR #2737 which may be fixing this issue, the images still need to be published though.
@tjbck commented on GitHub (Jun 2, 2024):
One way to find out 😂
@DavidZidar commented on GitHub (Jun 2, 2024):
I spent the last 30 minutes trying to make sense of these build steps, but I have never used these docker actions before and find the documentation lacking so take this info with a grain of salt.
But looking at the logs it seems that one of the build steps failed because
latestwas used for caching, The PR #2737 solves this by setting latest to false in the flavor input which seems correct.However, it seems to me like
type=ref,event=tagshould still be used, and I can't figure out what${{ github.ref_type == 'tag' && 'type=raw,value=main' || '' }}is supposed to be doing. That said, you might be able to omit thetagspart entirely because it uses these values by default:Or maybe you could use semver
type=semver,pattern={{version}}.So maybe like this since you run that workflow for both branches
mainanddevas well as for semver tags, but at this point I'm guessing:@not-a-ethan commented on GitHub (Jun 3, 2024):
@justinh-rahb can I ask why you closed this issue? This still appears to be an issue with the latest commit to both the main and dev branches failing tests and when I try and install it goes back to 0.1.124
@justinh-rahb commented on GitHub (Jun 3, 2024):
Alright @not-a-ethan, re-opened. Got anything to add? We have a
v0.2.2tag now, so I took that to mean the issue was resolved.@DavidZidar commented on GitHub (Jun 3, 2024):
I just pulled the image with version tag 0.2.2 and it seems to be working fine here.
@not-a-ethan commented on GitHub (Jun 3, 2024):
@justinh-rahb @DavidZidar That could be the issue. I am pulling from
:maininstead of:0.2.2. Currently pulling, dont have great wifi right now so going to take a little bit.@not-a-ethan commented on GitHub (Jun 3, 2024):
@justinh-rahb @DavidZidar Didnt work, still 0.1.124. I ran
sudo docker ps -aandsudo docker images -aand nothing shows up for either. Then I run these and nothing is updated@justinh-rahb commented on GitHub (Jun 3, 2024):
You must have some very aggressive caching going on then... try ensuring you've cleared any possible cached copies.
@not-a-ethan commented on GitHub (Jun 3, 2024):
@justinh-rahb That weird, I forgot about the site and cleared all cached items in my browser (FF dev edition) and its still 0.1.124. I run

sudo docker ps -aandsudo docker images -aand they both show it being0.2.2.@not-a-ethan commented on GitHub (Jun 3, 2024):
With some more experimentation I relised its a different issue (I think). I removed all of the open web ui stuff and closed my WSL terminal (and quit everything in task manager), forgot
locatlhost:8080and cleared cache. Then I refreshed the page and I gotUnable to Connect(expected). Opened my WSL terminal and I could accesslocalhost:8080again without running any commands.I ran
ps auxand I dont see anything that hasopen-webuior anything along the name of that. I do have some other docker stuff though (see below)@justinh-rahb commented on GitHub (Jun 3, 2024):
Alright it seems clear now your issue is unrelated to this thread, and the original poster seems to have had their issue resolved to their satisfaction. I'm closing this again, but please open a thread in the Discussions area or jump into our Discord #troubleshooting channel if you would like more assistance.
@DavidZidar commented on GitHub (Jun 3, 2024):
I am indeed satisfied. Thank you guys for Open WebUI, it's great!