github-starred/open-webui
2
0
Fork 0
mirror of https://github.com/open-webui/open-webui.git synced 2026-07-16 06:03:26 -05:00
Code Issues 2.4k Packages Projects Releases 129 Wiki Activity

[GH-ISSUE #16240] issue: Cannot build the docker image using Dockerfile #88576

New Issue
Closed
opened 2026-05-15 13:14:13 -05:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-05-15 13:14:13 -05:00
Owner
Copy Link

Originally created by @bmkor on GitHub (Aug 3, 2025).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/16240

Check Existing Issues

  • I have searched the existing issues and discussions.
  • I am using the latest version of Open WebUI.

Installation Method

Git Clone

Open WebUI Version

v0.6.18

Ollama Version (if applicable)

No response

Operating System

Ubuntu 22.04

Browser (if applicable)

No response

Confirmation

  • I have read and followed all instructions in README.md.
  • I am using the latest version of both Open WebUI and Ollama.
  • I have included the browser console logs.
  • I have included the Docker container logs.
  • I have provided every relevant configuration, setting, and environment variable used in my setup.
  • I have clearly listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc).
  • I have documented step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation. My steps:
  • Start with the initial platform/version/OS and dependencies used,
  • Specify exact install/launch/configure commands,
  • List URLs visited, user input (incl. example values/emails/passwords if needed),
  • Describe all options and toggles enabled or changed,
  • Include any files or environmental changes,
  • Identify the expected and actual result at each stage,
  • Ensure any reasonably skilled user can follow and hit the same issue.

Expected Behavior

Successfully built the Docker image using the Dockerfile in the project. This has no issue up to v0.6.15

Actual Behavior

Docker image cannot be built starting from v0.6.16.

Steps to Reproduce

  1. Git clone the project to our self-hosted gitlab
  2. Build the openwebui docker image via CI/CD
  3. The image could be built until v0.6.15.
  4. No change on the Dockerfile but cannot be built starting from v0.6.16 and has been failed up to v0.6.18.
  5. While the log was said to be network issue (as suggested by AI), we checked our network and expanded the timeout; it still failed miserably.

Logs & Screenshots

The error log extracted from CI/CD

INFO[0910] Taking snapshot of full filesystem...        
INFO[0911] COPY package.json package-lock.json RootCA.crt ./ 
INFO[0911] Taking snapshot of files...                  
INFO[0911] COPY onnxruntime-binaries/ /tmp/onnxruntime/ 
INFO[0911] Taking snapshot of files...                  
INFO[0912] RUN ONNXRUNTIME_NODE_INSTALL=skip npm ci --legacy-peer-deps &&     mkdir -p /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64 &&     cp -r /tmp/onnxruntime/* /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64/ 
INFO[0912] Cmd: /bin/sh                                 
INFO[0912] Args: [-c ONNXRUNTIME_NODE_INSTALL=skip npm ci --legacy-peer-deps &&     mkdir -p /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64 &&     cp -r /tmp/onnxruntime/* /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64/] 
INFO[0912] Running: [/bin/sh -c ONNXRUNTIME_NODE_INSTALL=skip npm ci --legacy-peer-deps &&     mkdir -p /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64 &&     cp -r /tmp/onnxruntime/* /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64/] 
npm error code 1
npm error path /app/node_modules/onnxruntime-node
npm error command failed
npm error command sh -c node ./script/install
npm error Downloading "https://github.com/microsoft/onnxruntime/releases/download/v1.20.1/onnxruntime-linux-x64-gpu-1.20.1.tgz"...
npm error Extracting "libonnxruntime_providers_cuda.so" to "/app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64"...
npm error node:events:496
npm error       throw er; // Unhandled 'error' event
npm error       ^
npm error
npm error TypeError: terminated
npm error     at Fetch.onAborted (node:internal/deps/undici/undici:11132:53)
npm error     at Fetch.emit (node:events:530:35)
npm error     at Fetch.terminate (node:internal/deps/undici/undici:10290:14)
npm error     at Object.onError (node:internal/deps/undici/undici:11253:38)
npm error     at Request.onError (node:internal/deps/undici/undici:2094:31)
npm error     at Object.errorRequest (node:internal/deps/undici/undici:1591:17)
npm error     at TLSSocket.<anonymous> (node:internal/deps/undici/undici:6319:16)
npm error     at TLSSocket.emit (node:events:530:35)
npm error     at node:net:351:12
npm error     at TCP.done (node:_tls_wrap:650:7)
npm error Emitted 'error' event on Readable instance at:
npm error     at emitErrorNT (node:internal/streams/destroy:170:8)
npm error     at emitErrorCloseNT (node:internal/streams/destroy:129:3)
npm error     at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
npm error   [cause]: SocketError: other side closed
npm error       at TLSSocket.<anonymous> (node:internal/deps/undici/undici:6294:28)
npm error       at TLSSocket.emit (node:events:530:35)
npm error       at endReadableNT (node:internal/streams/readable:1698:12)
npm error       at process.processTicksAndRejections (node:internal/process/task_queues:90:21) {
npm error     code: 'UND_ERR_SOCKET',
npm error     socket: {
npm error       localAddress: '10.244.1.152',
npm error       localPort: 58314,
npm error       remoteAddress: '185.199.108.133',
npm error       remotePort: 443,
npm error       remoteFamily: 'IPv4',
npm error       timeout: undefined,
npm error       bytesWritten: 1102,
npm error       bytesRead: 10486569
npm error     }
npm error   }
npm error }
npm error
npm error Node.js v22.16.0
npm notice
npm notice New major version of npm available! 10.9.2 -> 11.5.2
npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.5.2
npm notice To update run: npm install -g npm@11.5.2
npm notice
npm error A complete log of this run can be found in: /root/.npm/_logs/2025-08-03T14_09_18_872Z-debug-0.log
error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1

Additional Information

While the log was said to be network issue (as suggested by AI), we checked our network and expanded the timeout, and tried to skip the onnx gpu installation but it all still failed miserably. :(

Grateful if you would give us some hints on how to solve it. Thanks in advance.

Originally created by @bmkor on GitHub (Aug 3, 2025). Original GitHub issue: https://github.com/open-webui/open-webui/issues/16240 ### Check Existing Issues - [x] I have searched the existing issues and discussions. - [x] I am using the latest version of Open WebUI. ### Installation Method Git Clone ### Open WebUI Version v0.6.18 ### Ollama Version (if applicable) _No response_ ### Operating System Ubuntu 22.04 ### Browser (if applicable) _No response_ ### Confirmation - [x] I have read and followed all instructions in `README.md`. - [x] I am using the latest version of **both** Open WebUI and Ollama. - [x] I have included the browser console logs. - [x] I have included the Docker container logs. - [x] I have **provided every relevant configuration, setting, and environment variable used in my setup.** - [x] I have clearly **listed every relevant configuration, custom setting, environment variable, and command-line option that influences my setup** (such as Docker Compose overrides, .env values, browser settings, authentication configurations, etc). - [x] I have documented **step-by-step reproduction instructions that are precise, sequential, and leave nothing to interpretation**. My steps: - Start with the initial platform/version/OS and dependencies used, - Specify exact install/launch/configure commands, - List URLs visited, user input (incl. example values/emails/passwords if needed), - Describe all options and toggles enabled or changed, - Include any files or environmental changes, - Identify the expected and actual result at each stage, - Ensure any reasonably skilled user can follow and hit the same issue. ### Expected Behavior Successfully built the Docker image using the Dockerfile in the project. This has no issue up to v0.6.15 ### Actual Behavior Docker image cannot be built starting from v0.6.16. ### Steps to Reproduce 1. Git clone the project to our self-hosted gitlab 2. Build the openwebui docker image via CI/CD 3. The image could be built until v0.6.15. 4. No change on the Dockerfile but cannot be built starting from v0.6.16 and has been failed up to v0.6.18. 5. While the log was said to be network issue (as suggested by AI), we checked our network and expanded the timeout; it still failed miserably. ### Logs & Screenshots The error log extracted from CI/CD ``` INFO[0910] Taking snapshot of full filesystem... INFO[0911] COPY package.json package-lock.json RootCA.crt ./ INFO[0911] Taking snapshot of files... INFO[0911] COPY onnxruntime-binaries/ /tmp/onnxruntime/ INFO[0911] Taking snapshot of files... INFO[0912] RUN ONNXRUNTIME_NODE_INSTALL=skip npm ci --legacy-peer-deps && mkdir -p /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64 && cp -r /tmp/onnxruntime/* /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64/ INFO[0912] Cmd: /bin/sh INFO[0912] Args: [-c ONNXRUNTIME_NODE_INSTALL=skip npm ci --legacy-peer-deps && mkdir -p /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64 && cp -r /tmp/onnxruntime/* /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64/] INFO[0912] Running: [/bin/sh -c ONNXRUNTIME_NODE_INSTALL=skip npm ci --legacy-peer-deps && mkdir -p /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64 && cp -r /tmp/onnxruntime/* /app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64/] npm error code 1 npm error path /app/node_modules/onnxruntime-node npm error command failed npm error command sh -c node ./script/install npm error Downloading "https://github.com/microsoft/onnxruntime/releases/download/v1.20.1/onnxruntime-linux-x64-gpu-1.20.1.tgz"... npm error Extracting "libonnxruntime_providers_cuda.so" to "/app/node_modules/onnxruntime-node/bin/napi-v3/linux/x64"... npm error node:events:496 npm error throw er; // Unhandled 'error' event npm error ^ npm error npm error TypeError: terminated npm error at Fetch.onAborted (node:internal/deps/undici/undici:11132:53) npm error at Fetch.emit (node:events:530:35) npm error at Fetch.terminate (node:internal/deps/undici/undici:10290:14) npm error at Object.onError (node:internal/deps/undici/undici:11253:38) npm error at Request.onError (node:internal/deps/undici/undici:2094:31) npm error at Object.errorRequest (node:internal/deps/undici/undici:1591:17) npm error at TLSSocket.<anonymous> (node:internal/deps/undici/undici:6319:16) npm error at TLSSocket.emit (node:events:530:35) npm error at node:net:351:12 npm error at TCP.done (node:_tls_wrap:650:7) npm error Emitted 'error' event on Readable instance at: npm error at emitErrorNT (node:internal/streams/destroy:170:8) npm error at emitErrorCloseNT (node:internal/streams/destroy:129:3) npm error at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { npm error [cause]: SocketError: other side closed npm error at TLSSocket.<anonymous> (node:internal/deps/undici/undici:6294:28) npm error at TLSSocket.emit (node:events:530:35) npm error at endReadableNT (node:internal/streams/readable:1698:12) npm error at process.processTicksAndRejections (node:internal/process/task_queues:90:21) { npm error code: 'UND_ERR_SOCKET', npm error socket: { npm error localAddress: '10.244.1.152', npm error localPort: 58314, npm error remoteAddress: '185.199.108.133', npm error remotePort: 443, npm error remoteFamily: 'IPv4', npm error timeout: undefined, npm error bytesWritten: 1102, npm error bytesRead: 10486569 npm error } npm error } npm error } npm error npm error Node.js v22.16.0 npm notice npm notice New major version of npm available! 10.9.2 -> 11.5.2 npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.5.2 npm notice To update run: npm install -g npm@11.5.2 npm notice npm error A complete log of this run can be found in: /root/.npm/_logs/2025-08-03T14_09_18_872Z-debug-0.log error building image: error building stage: failed to execute command: waiting for process to exit: exit status 1 ``` ### Additional Information While the log was said to be network issue (as suggested by AI), we checked our network and expanded the timeout, and tried to skip the onnx gpu installation but it all still failed miserably. :( Grateful if you would give us some hints on how to solve it. Thanks in advance.
GiteaMirror added the bug label 2026-05-15 13:14:13 -05:00
GiteaMirror commented 2026-05-15 13:14:17 -05:00
Author
Owner
Copy Link

@tjbck commented on GitHub (Aug 3, 2025):

We're unable to reproduce, keep us updated!

<!-- gh-comment-id:3148541761 --> @tjbck commented on GitHub (Aug 3, 2025): We're unable to reproduce, keep us updated!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
confirmed
confirmed issue
core
documentation
enhancement
good first issue
help wanted
non-core
pull-request
Mirrored from GitHub Pull Request
 python
question
testing wanted
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/open-webui#88576
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?