[GH-ISSUE #5288] Building docker container fails

gitea-mirror commented

2026-05-05 14:35:00 -06:00

Owner

Originally created by @hrvylein on GitHub (Apr 13, 2026).
Original GitHub issue: https://github.com/fatedier/frp/issues/5288

Bug Description

Building the docker container fails in the first step when building web assets due to missing shared components.

docker build -t test/frps:0.68.0 --file dockerfiles/Dockerfile-for-frps .

Error message:

5.285 ✗ Build failed in 2.74s
5.286 error during build:
5.286 [vite:load-fallback] Could not load /web/shared/components/ActionButton.vue (imported by src/views/Proxies.vue?vue&type=script&setup=true&lang.ts): ENOENT: no such file or directory, open '/web/shared/components/ActionButton.vue'
5.286     at async open (node:internal/fs/promises:639:25)
5.286     at async Object.readFile (node:internal/fs/promises:1249:14)
5.286     at async Object.handler (file:///web/frps/node_modules/vite/dist/node/chunks/config.js:33173:21)
5.286     at async PluginDriver.hookFirstAndGetPlugin (file:///web/frps/node_modules/rollup/dist/es/shared/node-entry.js:22849:28)
5.286     at async file:///web/frps/node_modules/rollup/dist/es/shared/node-entry.js:21833:33
5.286     at async Queue.work (file:///web/frps/node_modules/rollup/dist/es/shared/node-entry.js:23077:32)
5.456 ERROR: "build-only" exited with 1.

frpc Version

0.68.0

frps Version

0.68.0

System Architecture

linux/amd64

Configurations

not needed

Logs

No response

Steps to reproduce

...

Affected area

Docs
Installation
Performance and Scalability
Security
User Experience
Test and Release
Developer Infrastructure
Client Plugin
Server Plugin
Extensions
Others

Originally created by @hrvylein on GitHub (Apr 13, 2026). Original GitHub issue: https://github.com/fatedier/frp/issues/5288 ### Bug Description Building the docker container fails in the first step when building web assets due to missing shared components. `docker build -t test/frps:0.68.0 --file dockerfiles/Dockerfile-for-frps .` Error message: ``` 5.285 ✗ Build failed in 2.74s 5.286 error during build: 5.286 [vite:load-fallback] Could not load /web/shared/components/ActionButton.vue (imported by src/views/Proxies.vue?vue&type=script&setup=true&lang.ts): ENOENT: no such file or directory, open '/web/shared/components/ActionButton.vue' 5.286 at async open (node:internal/fs/promises:639:25) 5.286 at async Object.readFile (node:internal/fs/promises:1249:14) 5.286 at async Object.handler (file:///web/frps/node_modules/vite/dist/node/chunks/config.js:33173:21) 5.286 at async PluginDriver.hookFirstAndGetPlugin (file:///web/frps/node_modules/rollup/dist/es/shared/node-entry.js:22849:28) 5.286 at async file:///web/frps/node_modules/rollup/dist/es/shared/node-entry.js:21833:33 5.286 at async Queue.work (file:///web/frps/node_modules/rollup/dist/es/shared/node-entry.js:23077:32) 5.456 ERROR: "build-only" exited with 1. ``` ### frpc Version 0.68.0 ### frps Version 0.68.0 ### System Architecture linux/amd64 ### Configurations not needed ### Logs _No response_ ### Steps to reproduce 1. 2. 3. ... ### Affected area - [ ] Docs - [x] Installation - [ ] Performance and Scalability - [ ] Security - [ ] User Experience - [ ] Test and Release - [ ] Developer Infrastructure - [ ] Client Plugin - [ ] Server Plugin - [ ] Extensions - [ ] Others

gitea-mirror

2026-05-05 14:35:00 -06:00

closed this issue
added the
lifecycle/stale
label

gitea-mirror commented

2026-05-05 14:35:03 -06:00

Author

Owner

@fatedier commented on GitHub (Apr 14, 2026):

Please retry with the latest code. This build issue appears to have already been fixed in the current Dockerfile/frontend layout.

@fatedier commented on GitHub (Apr 14, 2026): Please retry with the latest code. This build issue appears to have already been fixed in the current Dockerfile/frontend layout.

gitea-mirror commented

2026-05-05 14:35:03 -06:00

Author

Owner

@github-actions[bot] commented on GitHub (Apr 29, 2026):

Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.

@github-actions[bot] commented on GitHub (Apr 29, 2026): Issues go stale after 14d of inactivity. Stale issues rot after an additional 3d of inactivity and eventually close.