starred/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-02-05 00:29:55 +03:00
Code Issues 11 Packages Projects Releases 10 Wiki Activity

Tracktor error line 159 & 1345 #1674

New Issue
Closed
opened 2026-02-05 01:55:13 +03:00 by OVERLORD · 2 comments
OVERLORD commented 2026-02-05 01:55:13 +03:00
Owner
Copy Link

Originally created by @javijuji on GitHub (Sep 25, 2025).

✅ Have you read and understood the above guidelines?

yes

📜 What is the name of the script you are using?

Tracktor

📂 What was the exact command used to execute the script?

bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/tracktor.sh)"

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-2-pve)

📝 Provide a clear and concise description of the issue.

🚀 Creating a tracktor LXC using the above advanced settings
✔️ Storage local (Free: 205.9GB Used: 237.8MB) [Template]
✔️ Storage nvme-pool (Free: 1.7TB Used: 68.4GB) [Container]
✔️ Cluster is quorate
✔️ Template debian-13-standard_13.1-1_amd64.tar.zst [local]
✔️ LXC Container 108 was successfully created.
✔️ Started LXC Container
💡 No network in LXC yet (try 1/10) – waiting...
💡 No network in LXC yet (try 2/10) – waiting...
✔️ Network in LXC is reachable (ping)
✔️ Customized LXC Container
✔️ Set up Container OS
✔️ Network Connected: xx.xx.xx.xx
✔️ IPv4 Internet Connected
✖️ IPv6 Internet Not Connected
✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
Hit:1 http://security.debian.org trixie-security InRelease
Hit:2 http://deb.debian.org/debian trixie InRelease
Hit:3 http://deb.debian.org/debian trixie-updates InRelease
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 systemd systemd-sysv systemd-timesyncd udev
9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 7919 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://deb.debian.org/debian trixie-updates/main amd64 libsystemd0 amd64 257.8-1deb13u2 [454 kB]
Get:2 http://deb.debian.org/debian trixie-updates/main amd64 systemd-sysv amd64 257.8-1deb13u2 [64.5 kB]
Get:3 http://deb.debian.org/debian trixie-updates/main amd64 libnss-systemd amd64 257.8-1deb13u2 [219 kB]
Get:4 http://deb.debian.org/debian trixie-updates/main amd64 libpam-systemd amd64 257.8-1deb13u2 [297 kB]
Get:5 http://deb.debian.org/debian trixie-updates/main amd64 libsystemd-shared amd64 257.8-1deb13u2 [2151 kB]
Get:6 http://deb.debian.org/debian trixie-updates/main amd64 systemd amd64 257.8-1deb13u2 [3099 kB]
Get:7 http://deb.debian.org/debian trixie-updates/main amd64 systemd-timesyncd amd64 257.8-1deb13u2 [92.9 kB]
Get:8 http://deb.debian.org/debian trixie-updates/main amd64 udev amd64 257.8-1deb13u2 [1390 kB]
Get:9 http://deb.debian.org/debian trixie-updates/main amd64 libudev1 amd64 257.8-1deb13u2 [152 kB]
Fetched 7919 kB in 0s (27.7 MB/s)
apt-listchanges: Reading changelogs...
(Reading database ... 20169 files and directories currently installed.)
Preparing to unpack .../libsystemd0_257.8-1deb13u2_amd64.deb ...
Unpacking libsystemd0:amd64 (257.8-1deb13u2) over (257.8-1deb13u1) ...
Setting up libsystemd0:amd64 (257.8-1deb13u2) ...
(Reading database ... 20169 files and directories currently installed.)
Preparing to unpack .../systemd-sysv_257.8-1deb13u2_amd64.deb ...
Unpacking systemd-sysv (257.8-1deb13u2) over (257.8-1deb13u1) ...
Preparing to unpack .../libnss-systemd_257.8-1deb13u2_amd64.deb ...
Unpacking libnss-systemd:amd64 (257.8-1deb13u2) over (257.8-1deb13u1) ...
Preparing to unpack .../libpam-systemd_257.8-1deb13u2_amd64.deb ...
Unpacking libpam-systemd:amd64 (257.8-1deb13u2) over (257.8-1deb13u1) ...
Preparing to unpack .../libsystemd-shared_257.8-1deb13u2_amd64.deb ...
Unpacking libsystemd-shared:amd64 (257.8-1deb13u2) over (257.8-1deb13u1) ...
Setting up libsystemd-shared:amd64 (257.8-1deb13u2) ...
(Reading database ... 20169 files and directories currently installed.)
Preparing to unpack .../systemd_257.8-1deb13u2_amd64.deb ...
Unpacking systemd (257.8-1deb13u2) over (257.8-1deb13u1) ...
Preparing to unpack .../systemd-timesyncd_257.8-1deb13u2_amd64.deb ...
Unpacking systemd-timesyncd (257.8-1deb13u2) over (257.8-1deb13u1) ...
Preparing to unpack .../udev_257.8-1deb13u2_amd64.deb ...
Unpacking udev (257.8-1deb13u2) over (257.8-1deb13u1) ...
Preparing to unpack .../libudev1_257.8-1deb13u2_amd64.deb ...
Unpacking libudev1:amd64 (257.8-1deb13u2) over (257.8-1deb13u1) ...
Setting up libudev1:amd64 (257.8-1deb13u2) ...
Setting up systemd (257.8-1deb13u2) ...
/usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring.
Setting up systemd-timesyncd (257.8-1deb13u2) ...
systemd-time-wait-sync.service is a disabled or a static unit not running, not starting it.
Setting up udev (257.8-1deb13u2) ...
systemd-udevd.service is a disabled or a static unit not running, not starting it.
Setting up systemd-sysv (257.8-1deb13u2) ...
Setting up libnss-systemd:amd64 (257.8-1deb13u2) ...
Setting up libpam-systemd:amd64 (257.8-1~deb13u2) ...
Processing triggers for man-db (2.13.1-1) ...
Processing triggers for dbus (1.16.2-2) ...
Processing triggers for shared-mime-info (2.4-5+b2) ...
Processing triggers for procps (2:4.0.4-9) ...
Processing triggers for libc-bin (2.41-12) ...
✔️ Updated Container OS
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Package 'nodejs' is not installed, so not removed
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.

removed 26 packages, and changed 78 packages in 2s

28 packages are looking for funding
run npm fund for details
✔️ Setup Node.js 22
✔️ Deployed: tracktor (0.3.9)

added 666 packages, and audited 669 packages in 14s

126 packages are looking for funding
run npm fund for details

9 vulnerabilities (4 low, 4 moderate, 1 high)

To address issues that do not require attention, run:
npm audit fix

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.

build
./scripts/build.sh

... Starting build process...
... Cleaning previous build artifacts...
... Creating build directories...
✓ Build directories created
... Installing dependencies...

removed 1 package, and audited 668 packages in 898ms

126 packages are looking for funding
run npm fund for details

9 vulnerabilities (4 low, 4 moderate, 1 high)

To address issues that do not require attention, run:
npm audit fix

To address all issues (including breaking changes), run:
npm audit fix --force

Run npm audit for details.
✓ Dependencies installed successfully
... Building workspaces...

backend@0.0.1 build
tsc && tsc-alias

frontend@0.0.1 build
vite build

▲ [WARNING] Cannot find base config file "./.svelte-kit/tsconfig.json" [tsconfig.json]

tsconfig.json:2:12:
  2 │   "extends": "./.svelte-kit/tsconfig.json",
    ╵              ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Running in mode : production
vite v7.1.3 building SSR bundle for production...
✓ 44 modules transformed.
✗ Build failed in 392ms
error during build:
[vite]: Rollup failed to resolve import "zod/v4" from "/opt/tracktor/app/frontend/src/lib/components/features/settings/SettingsSheet.svelte".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
build.rollupOptions.external
at viteLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34230:57)
at file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34268:73
at onwarn (file:///opt/tracktor/node_modules/@sveltejs/kit/src/exports/vite/index.js:879:9)
at file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34268:28
at onRollupLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34263:3)
at onLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34063:4)
at file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:20863:32
at Object.logger [as onLog] (file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:22745:9)
at ModuleLoader.handleInvalidResolvedId (file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:21489:26)
at file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:21447:26
npm error Lifecycle script build failed with error:
npm error code 1
npm error path /opt/tracktor/app/frontend
npm error workspace frontend@0.0.1
npm error location /opt/tracktor/app/frontend
npm error command failed
npm error command sh -c vite build
✗ Failed to build workspaces

[ERROR] in line 22: exit code 0: while executing command $STD npm run build

[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

🔄 Steps to reproduce the issue.

Ran the script in verbose mode. Tested default and advanced settings. Both result in error

❌ Paste the full error output (if available).

[vite]: Rollup failed to resolve import "zod/v4" from "/opt/tracktor/app/frontend/src/lib/components/features/settings/SettingsSheet.svelte".
This is most likely unintended because it can break your application at runtime.
If you do want to externalize this module explicitly add it to
build.rollupOptions.external
at viteLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34230:57)
at file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34268:73
at onwarn (file:///opt/tracktor/node_modules/@sveltejs/kit/src/exports/vite/index.js:879:9)
at file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34268:28
at onRollupLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34263:3)
at onLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34063:4)
at file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:20863:32
at Object.logger [as onLog] (file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:22745:9)
at ModuleLoader.handleInvalidResolvedId (file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:21489:26)
at file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:21447:26
npm error Lifecycle script build failed with error:
npm error code 1
npm error path /opt/tracktor/app/frontend
npm error workspace frontend@0.0.1
npm error location /opt/tracktor/app/frontend
npm error command failed
npm error command sh -c vite build
✗ Failed to build workspaces

[ERROR] in line 22: exit code 0: while executing command $STD npm run build

[ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)"

🖼️ Additional context (optional).

No response

Originally created by @javijuji on GitHub (Sep 25, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Tracktor ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/tracktor.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? pve-manager/9.0.10/deb1ca707ec72a89 (running kernel: 6.14.11-2-pve) ### 📝 Provide a clear and concise description of the issue. 🚀 Creating a tracktor LXC using the above advanced settings ✔️ Storage local (Free: 205.9GB Used: 237.8MB) [Template] ✔️ Storage nvme-pool (Free: 1.7TB Used: 68.4GB) [Container] ✔️ Cluster is quorate ✔️ Template debian-13-standard_13.1-1_amd64.tar.zst [local] ✔️ LXC Container 108 was successfully created. ✔️ Started LXC Container 💡 No network in LXC yet (try 1/10) – waiting... 💡 No network in LXC yet (try 2/10) – waiting... ✔️ Network in LXC is reachable (ping) ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: xx.xx.xx.xx ✔️ IPv4 Internet Connected ✖️ IPv6 Internet Not Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) Hit:1 http://security.debian.org trixie-security InRelease Hit:2 http://deb.debian.org/debian trixie InRelease Hit:3 http://deb.debian.org/debian trixie-updates InRelease Reading package lists... Done Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages will be upgraded: libnss-systemd libpam-systemd libsystemd-shared libsystemd0 libudev1 systemd systemd-sysv systemd-timesyncd udev 9 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. Need to get 7919 kB of archives. After this operation, 0 B of additional disk space will be used. Get:1 http://deb.debian.org/debian trixie-updates/main amd64 libsystemd0 amd64 257.8-1~deb13u2 [454 kB] Get:2 http://deb.debian.org/debian trixie-updates/main amd64 systemd-sysv amd64 257.8-1~deb13u2 [64.5 kB] Get:3 http://deb.debian.org/debian trixie-updates/main amd64 libnss-systemd amd64 257.8-1~deb13u2 [219 kB] Get:4 http://deb.debian.org/debian trixie-updates/main amd64 libpam-systemd amd64 257.8-1~deb13u2 [297 kB] Get:5 http://deb.debian.org/debian trixie-updates/main amd64 libsystemd-shared amd64 257.8-1~deb13u2 [2151 kB] Get:6 http://deb.debian.org/debian trixie-updates/main amd64 systemd amd64 257.8-1~deb13u2 [3099 kB] Get:7 http://deb.debian.org/debian trixie-updates/main amd64 systemd-timesyncd amd64 257.8-1~deb13u2 [92.9 kB] Get:8 http://deb.debian.org/debian trixie-updates/main amd64 udev amd64 257.8-1~deb13u2 [1390 kB] Get:9 http://deb.debian.org/debian trixie-updates/main amd64 libudev1 amd64 257.8-1~deb13u2 [152 kB] Fetched 7919 kB in 0s (27.7 MB/s) apt-listchanges: Reading changelogs... (Reading database ... 20169 files and directories currently installed.) Preparing to unpack .../libsystemd0_257.8-1~deb13u2_amd64.deb ... Unpacking libsystemd0:amd64 (257.8-1~deb13u2) over (257.8-1~deb13u1) ... Setting up libsystemd0:amd64 (257.8-1~deb13u2) ... (Reading database ... 20169 files and directories currently installed.) Preparing to unpack .../systemd-sysv_257.8-1~deb13u2_amd64.deb ... Unpacking systemd-sysv (257.8-1~deb13u2) over (257.8-1~deb13u1) ... Preparing to unpack .../libnss-systemd_257.8-1~deb13u2_amd64.deb ... Unpacking libnss-systemd:amd64 (257.8-1~deb13u2) over (257.8-1~deb13u1) ... Preparing to unpack .../libpam-systemd_257.8-1~deb13u2_amd64.deb ... Unpacking libpam-systemd:amd64 (257.8-1~deb13u2) over (257.8-1~deb13u1) ... Preparing to unpack .../libsystemd-shared_257.8-1~deb13u2_amd64.deb ... Unpacking libsystemd-shared:amd64 (257.8-1~deb13u2) over (257.8-1~deb13u1) ... Setting up libsystemd-shared:amd64 (257.8-1~deb13u2) ... (Reading database ... 20169 files and directories currently installed.) Preparing to unpack .../systemd_257.8-1~deb13u2_amd64.deb ... Unpacking systemd (257.8-1~deb13u2) over (257.8-1~deb13u1) ... Preparing to unpack .../systemd-timesyncd_257.8-1~deb13u2_amd64.deb ... Unpacking systemd-timesyncd (257.8-1~deb13u2) over (257.8-1~deb13u1) ... Preparing to unpack .../udev_257.8-1~deb13u2_amd64.deb ... Unpacking udev (257.8-1~deb13u2) over (257.8-1~deb13u1) ... Preparing to unpack .../libudev1_257.8-1~deb13u2_amd64.deb ... Unpacking libudev1:amd64 (257.8-1~deb13u2) over (257.8-1~deb13u1) ... Setting up libudev1:amd64 (257.8-1~deb13u2) ... Setting up systemd (257.8-1~deb13u2) ... /usr/lib/tmpfiles.d/legacy.conf:14: Duplicate line for path "/run/lock", ignoring. Setting up systemd-timesyncd (257.8-1~deb13u2) ... systemd-time-wait-sync.service is a disabled or a static unit not running, not starting it. Setting up udev (257.8-1~deb13u2) ... systemd-udevd.service is a disabled or a static unit not running, not starting it. Setting up systemd-sysv (257.8-1~deb13u2) ... Setting up libnss-systemd:amd64 (257.8-1~deb13u2) ... Setting up libpam-systemd:amd64 (257.8-1~deb13u2) ... Processing triggers for man-db (2.13.1-1) ... Processing triggers for dbus (1.16.2-2) ... Processing triggers for shared-mime-info (2.4-5+b2) ... Processing triggers for procps (2:4.0.4-9) ... Processing triggers for libc-bin (2.41-12) ... ✔️ Updated Container OS Reading package lists... Done Building dependency tree... Done Reading state information... Done Package 'nodejs' is not installed, so not removed 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. removed 26 packages, and changed 78 packages in 2s 28 packages are looking for funding run `npm fund` for details ✔️ Setup Node.js 22 ✔️ Deployed: tracktor (0.3.9) added 666 packages, and audited 669 packages in 14s 126 packages are looking for funding run `npm fund` for details 9 vulnerabilities (4 low, 4 moderate, 1 high) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. > build > ./scripts/build.sh ... Starting build process... ... Cleaning previous build artifacts... ... Creating build directories... ✓ Build directories created ... Installing dependencies... removed 1 package, and audited 668 packages in 898ms 126 packages are looking for funding run `npm fund` for details 9 vulnerabilities (4 low, 4 moderate, 1 high) To address issues that do not require attention, run: npm audit fix To address all issues (including breaking changes), run: npm audit fix --force Run `npm audit` for details. ✓ Dependencies installed successfully ... Building workspaces... > backend@0.0.1 build > tsc && tsc-alias > frontend@0.0.1 build > vite build ▲ [WARNING] Cannot find base config file "./.svelte-kit/tsconfig.json" [tsconfig.json] tsconfig.json:2:12: 2 │ "extends": "./.svelte-kit/tsconfig.json", ╵ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Running in mode : production vite v7.1.3 building SSR bundle for production... ✓ 44 modules transformed. ✗ Build failed in 392ms error during build: [vite]: Rollup failed to resolve import "zod/v4" from "/opt/tracktor/app/frontend/src/lib/components/features/settings/SettingsSheet.svelte". This is most likely unintended because it can break your application at runtime. If you do want to externalize this module explicitly add it to `build.rollupOptions.external` at viteLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34230:57) at file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34268:73 at onwarn (file:///opt/tracktor/node_modules/@sveltejs/kit/src/exports/vite/index.js:879:9) at file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34268:28 at onRollupLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34263:3) at onLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34063:4) at file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:20863:32 at Object.logger [as onLog] (file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:22745:9) at ModuleLoader.handleInvalidResolvedId (file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:21489:26) at file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:21447:26 npm error Lifecycle script `build` failed with error: npm error code 1 npm error path /opt/tracktor/app/frontend npm error workspace frontend@0.0.1 npm error location /opt/tracktor/app/frontend npm error command failed npm error command sh -c vite build ✗ Failed to build workspaces [ERROR] in line 22: exit code 0: while executing command $STD npm run build [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" ### 🔄 Steps to reproduce the issue. Ran the script in verbose mode. Tested default and advanced settings. Both result in error ### ❌ Paste the full error output (if available). [vite]: Rollup failed to resolve import "zod/v4" from "/opt/tracktor/app/frontend/src/lib/components/features/settings/SettingsSheet.svelte". This is most likely unintended because it can break your application at runtime. If you do want to externalize this module explicitly add it to `build.rollupOptions.external` at viteLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34230:57) at file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34268:73 at onwarn (file:///opt/tracktor/node_modules/@sveltejs/kit/src/exports/vite/index.js:879:9) at file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34268:28 at onRollupLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34263:3) at onLog (file:///opt/tracktor/node_modules/vite/dist/node/chunks/dep-Bj7gA1-0.js:34063:4) at file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:20863:32 at Object.logger [as onLog] (file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:22745:9) at ModuleLoader.handleInvalidResolvedId (file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:21489:26) at file:///opt/tracktor/node_modules/rollup/dist/es/shared/node-entry.js:21447:26 npm error Lifecycle script `build` failed with error: npm error code 1 npm error path /opt/tracktor/app/frontend npm error workspace frontend@0.0.1 npm error location /opt/tracktor/app/frontend npm error command failed npm error command sh -c vite build ✗ Failed to build workspaces [ERROR] in line 22: exit code 0: while executing command $STD npm run build [ERROR] in line 1345: exit code 0: while executing command lxc-attach -n "$CTID" -- bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/install/${var_install}.sh)" ### 🖼️ Additional context (optional). _No response_
OVERLORD added the bugexternal labels 2026-02-05 01:55:13 +03:00
OVERLORD commented 2026-02-05 01:55:19 +03:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 25, 2025):

@CrazyWolf13

@MickLesk commented on GitHub (Sep 25, 2025): @CrazyWolf13
OVERLORD commented 2026-02-05 01:55:23 +03:00
Author
Owner
Copy Link

@CrazyWolf13 commented on GitHub (Sep 25, 2025):

@javijuji This is an upstream issue, I reported this to the tracktor developer, feel free to subscribe to the isse, so you get a reply when it's fixed :)

https://github.com/javedh-dev/tracktor/issues/90

I'll close this here in the meantime.

@CrazyWolf13 commented on GitHub (Sep 25, 2025): @javijuji This is an upstream issue, I reported this to the tracktor developer, feel free to subscribe to the isse, so you get a reply when it's fixed :) https://github.com/javedh-dev/tracktor/issues/90 I'll close this here in the meantime.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Implemented in VED waiting push to Main
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
in project pipeline
invalid
investigation
json
maintenance
needs triage
new script
new script
nice to have
not a script issue
not planned
organization
pull-request
Mirrored from GitHub Pull Request
 question
refactor
rename script
security
update script
website
wontdo
🛑 Failure to comply with the guidelines
No Label bug external
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
OVERLORD
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: starred/ProxmoxVE#1674
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?