open-webui/oikb
1
0
Fork 0
mirror of https://github.com/open-webui/oikb.git synced 2026-11-05 01:27:25 +00:00
Code Issues 72 Projects Packages Wiki Activity

[GH-ISSUE #126] No Docker Image built for Release v0.5.0 #74

New issue
Open
opened 2026-10-18 21:14:06 +00:00 by bsakaguchi · 5 comments
bsakaguchi commented 2026-10-18 21:14:06 +00:00
Owner
Copy link

Originally created by @TobiasGoerke on GitHub (Sep 18, 2026).
Original GitHub issue: https://github.com/open-webui/oikb/issues/126

See failing action: https://github.com/open-webui/oikb/actions/runs/35141437341

Originally created by @TobiasGoerke on GitHub (Sep 18, 2026). Original GitHub issue: https://github.com/open-webui/oikb/issues/126 See failing action: https://github.com/open-webui/oikb/actions/runs/35141437341
bsakaguchi commented 2026-10-18 21:14:07 +00:00
Author
Owner
Copy link

@rnogueira-tech commented on GitHub (Sep 21, 2026):

Yes it's falling:
"
:~/docker/vllm-openai> docker compose up -d --no-deps oikb
[+] Running 1/1
✘ oikb Error failed to resolve reference "ghcr.io/open-webui/oikb:0.5.0": ghcr.io/open-webui/oikb:0.5.0: not found 0.7s
Error response from daemon: failed to resolve reference "ghcr.io/open-webui/oikb:0.5.0": ghcr.io/open-webui/oikb:0.5.0: not found"

<!-- gh-comment-id:5762196260 --> @rnogueira-tech commented on GitHub (Sep 21, 2026): Yes it's falling: " :~/docker/vllm-openai> docker compose up -d --no-deps oikb [+] Running 1/1 ✘ oikb Error failed to resolve reference "ghcr.io/open-webui/oikb:0.5.0": ghcr.io/open-webui/oikb:0.5.0: not found 0.7s Error response from daemon: failed to resolve reference "ghcr.io/open-webui/oikb:0.5.0": ghcr.io/open-webui/oikb:0.5.0: not found"
bsakaguchi commented 2026-10-18 21:14:07 +00:00
Author
Owner
Copy link

@TrilceAC commented on GitHub (Sep 29, 2026):

The error occurs while running github action https://github.com/open-webui/oikb/actions/runs/35141437341/job/104946683561

pymupdf fails to build from source on linux/arm64 + Alpine (musl), preventing all 0.5.0 tags from being published

build-release (linux/arm64, alpine, Dockerfile.alpine) fails during uv sync --extra all while compiling pymupdf==1.28.2 from source (no musl/arm64 wheel available). The generated SWIG C++ bindings reference PyString_FromString — a Python 2-only API — which doesn't exist under Python 3.11, causing a hard compile error (see log).

Since merge-release/merge-release-alpine depend on the full build-release matrix, no :latest/:0.5.0 tags were published at all — even though the non-Alpine Dockerfile succeeded on both amd64 and arm64.

Possible fixes: pin an older/patched pymupdf version compatible with this SWIG target, or scope the workflow so a single matrix failure doesn't block unrelated tags from being pushed.

<!-- gh-comment-id:5892144482 --> @TrilceAC commented on GitHub (Sep 29, 2026): The error occurs while running github action https://github.com/open-webui/oikb/actions/runs/35141437341/job/104946683561 **pymupdf fails to build from source on linux/arm64 + Alpine (musl)**, preventing all 0.5.0 tags from being published build-release (linux/arm64, alpine, Dockerfile.alpine) fails during uv sync --extra all while compiling pymupdf==1.28.2 from source (no musl/arm64 wheel available). The generated SWIG C++ bindings reference PyString_FromString — a Python 2-only API — which doesn't exist under Python 3.11, causing a hard compile error (see [log](https://github.com/open-webui/oikb/actions/runs/35141437341/job/104946683561)). Since merge-release/merge-release-alpine depend on the full build-release matrix, no :latest/:0.5.0 tags were published at all — even though the non-Alpine Dockerfile succeeded on both amd64 and arm64. Possible fixes: pin an older/patched pymupdf version compatible with this SWIG target, or scope the workflow so a single matrix failure doesn't block unrelated tags from being pushed.
bsakaguchi commented 2026-10-18 21:14:07 +00:00
Author
Owner
Copy link

@MoeLa commented on GitHub (Sep 29, 2026):

Until this is fixed, I use a custom Dockerfile:

FROM python:3.12-slim

RUN pip install --no-cache-dir "oikb[gdrive]==0.5.0"

WORKDIR /app
ENTRYPOINT ["oikb"]

A python base image is used to install oikb-0.5.0 (in my case with the gdrive connector).

Hope, that helps!

<!-- gh-comment-id:5900988954 --> @MoeLa commented on GitHub (Sep 29, 2026): Until this is fixed, I use a custom `Dockerfile`: ``` FROM python:3.12-slim RUN pip install --no-cache-dir "oikb[gdrive]==0.5.0" WORKDIR /app ENTRYPOINT ["oikb"] ``` A python base image is used to install `oikb-0.5.0` (in my case with the gdrive connector). Hope, that helps!
bsakaguchi commented 2026-10-18 21:14:07 +00:00
Author
Owner
Copy link

@TrilceAC commented on GitHub (Sep 30, 2026):

@MoeLa , I took a different approach. The original Dockerfile just works fine. The broken integration that has prevented the 0.5.0 images to be released is the dockerfile for the image based on alpine. I've just built the generic locally:

git clone https://github.com/open-webui/oikb.git
cd oikb
docker build -t oikb:local .

I use it in a docker-compose.yaml

services:
  oikb:
    # 0.5.0 not yet available due to a broken pipeline building Alpine image
    # image: ghcr.io/open-webui/oikb:latest

    # Using locally built image, and dorp it when this gets fixed
    image: oikb:local
    ...
<!-- gh-comment-id:5905681449 --> @TrilceAC commented on GitHub (Sep 30, 2026): @MoeLa , I took a different approach. The original Dockerfile just works fine. The broken integration that has prevented the 0.5.0 images to be released is the dockerfile for the image based on alpine. I've just built the generic locally: ```bash git clone https://github.com/open-webui/oikb.git cd oikb docker build -t oikb:local . ``` I use it in a docker-compose.yaml ```yml services: oikb: # 0.5.0 not yet available due to a broken pipeline building Alpine image # image: ghcr.io/open-webui/oikb:latest # Using locally built image, and dorp it when this gets fixed image: oikb:local ... ```
bsakaguchi commented 2026-10-18 21:14:07 +00:00
Author
Owner
Copy link

@Go2Engle commented on GitHub (Oct 1, 2026):

You can also use the below to build without first having to pull repo down and build.

services:
  oikb:
    build:
      context: https://github.com/open-webui/oikb.git#v0.5.0
    image: oikb-local:0.5.0
<!-- gh-comment-id:5929928525 --> @Go2Engle commented on GitHub (Oct 1, 2026): You can also use the below to build without first having to pull repo down and build. ```yaml services: oikb: build: context: https://github.com/open-webui/oikb.git#v0.5.0 image: oikb-local:0.5.0 ```
Sign in to join this conversation.
No Branch/Tag specified
Branches Tags
main
release
v0.6.0
v0.5.0
v0.4.0
v0.3.6
v0.3.5
v0.3.4
v0.3.3
v0.3.2
v0.3.1
v0.3.0
v0.2.9
v0.2.8
v0.2.7
v0.2.6
v0.2.5
v0.2.4
v0.2.3
v0.2.2
v0.2.1
v0.2.0
v0.1.3
v0.1.2
v0.1.1
v0.1.0
Labels
Clear labels   
pull-request
Mirrored from GitHub Pull Request

No labels
pull-request
Milestone
Clear milestone
No items
No milestone
Projects
Clear projects
No items
No project
Assignees
Clear assignees
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
open-webui/oikb#74
No description provided.