Devcontainer Setup, Stuck at Updating Frontend #11310
Replies: 7 comments 14 replies
-
|
also I tried to get the version of the dev-container and got this Python paths:
Executable /home/inventree/dev/venv/bin/python3
Environment /home/inventree/dev/venv
Invoke Tool /home/inventree/dev/venv/lib/python3.11/site-packages/invoke/__init__.py
Installation paths:
Base /home/inventree
Config /home/inventree/dev/config.yaml
Plugin File /home/inventree/dev/plugins.txt
Media /home/inventree/dev/media
Static /home/inventree/dev/static
Backup /home/inventree/dev/backup
Versions:
InvenTree 1.3.0 dev
API 453
Python 3.11.14
Django 5.2.11
Node v24.13.1
Yarn ! Corepack is about to download https://registry.yarnpkg.com/yarn/-/yarn-1.22.22.tgz
? Do you want to continue? [Y/n]
1.22.22
Environment:
Platform Devcontainer
Debug True
Commit hash: b568e82
Commit date: 2026-02-13 |
Beta Was this translation helpful? Give feedback.
-
|
this sounds a bit like #11282; maybe try re-downloading the repo and see if it works now; a fix is in master |
Beta Was this translation helpful? Give feedback.
-
Beta Was this translation helpful? Give feedback.
-
|
Tried the new update, got a little bit further than getting stuck at the updating front end but got this error code Compiling frontend translations
yarn run v1.22.22
$ lingui compile --typescript
Compiling message catalogs…
[2167811 ms] Port forwarding 58030 > 34715 > 34715: Local close with error
/home/inventree/src/frontend/node_modules/threads/dist/master/spawn.js:35
timeoutHandle = setTimeout(() => reject(Error(errorMessage)), timeoutInMs);
^
Error: Timeout: Did not receive an init message from worker after 10000ms. Make sure the worker calls expose().
at Timeout._onTimeout (/home/inventree/src/frontend/node_modules/threads/dist/master/spawn.js:35:53)
at listOnTimeout (node:internal/timers:605:17)
at process.processTimers (node:internal/timers:541:7)
Node.js v24.13.1
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
ERROR: InvenTree command failed: 'yarn run compile'
- Refer to the error messages in the log above for more information
What's next:
Try Docker Debug for seamless, persistent debugging tools in any container or image → docker debug 379f88d1afe022640261edf4cc5a1d41e35f6358a259176cbfabcd7175b0df51
Learn more at https://docs.docker.com/go/debug-cli/Tried to change to a older maintained version of Node.js and it went past the frontend develop part so hopefully it fixed that, but was thrown this later Collecting django-querycount==0.8.3 (from -r /home/inventree/src/backend/require
ments-dev.txt (line 394))
Downloading django-querycount-0.8.3.tar.gz (6.7 kB)
Installing build dependencies: started
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: still running...
Installing build dependencies: finished with status 'error'
error: subprocess-exited-with-error
× installing build dependencies for django-querycount did not run successfully
.
│ exit code: 1
╰─> [7 lines of output]
WARNING: Retrying (Retry(total=4, connect=None, read=None, redirect=None,
status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urlli
b3.connection.HTTPSConnection object at 0x7f4ee7d471d0>, 'Connection to pypi.org
timed out. (connect timeout=15)')': /simple/setuptools/
WARNING: Retrying (Retry(total=3, connect=None, read=None, redirect=None,
status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urlli
b3.connection.HTTPSConnection object at 0x7f4ee7d477d0>, 'Connection to pypi.org
timed out. (connect timeout=15)')': /simple/setuptools/
WARNING: Retrying (Retry(total=2, connect=None, read=None, redirect=None,
status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urlli
b3.connection.HTTPSConnection object at 0x7f4ee7d502d0>, 'Connection to pypi.org
timed out. (connect timeout=15)')': /simple/setuptools/
WARNING: Retrying (Retry(total=1, connect=None, read=None, redirect=None,
status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urlli
b3.connection.HTTPSConnection object at 0x7f4ee7d51090>, 'Connection to pypi.org
timed out. (connect timeout=15)')': /simple/setuptools/
WARNING: Retrying (Retry(total=0, connect=None, read=None, redirect=None,
status=None)) after connection broken by 'ConnectTimeoutError(<pip._vendor.urlli
b3.connection.HTTPSConnection object at 0x7f4ee7d51d10>, 'Connection to pypi.org
timed out. (connect timeout=15)')': /simple/setuptools/
ERROR: Could not find a version that satisfies the requirement setuptools>
=40.8.0 (from versions: none)
ERROR: No matching distribution found for setuptools>=40.8.0
[end of output]
note: This error originates from a subprocess, and is likely not a problem wit
h pip.
ERROR: Failed to build 'django-querycount' when installing build dependencies fo
r django-querycount
ERROR: InvenTree command failed: 'pip3 install --no-cache-dir --disable-pip-vers
ion-check -U --require-hashes -r /home/inventree/src/backend/requirements-dev.tx
t'
- Refer to the error messages in the log above for more information
im going to try and look into my network to see if I can see why it wouldnt connect, probably because of company wifi. |
Beta Was this translation helpful? Give feedback.
-
|
It works now, # Install packages required for frontend development
# This one did not work for me
# RUN apt install -y nodejs npm
#Install packages required for frontend development, oldest Maintenance LTS
RUN curl -fsSL https://deb.nodesource.com/setup_20.x | bash - && apt-get install -y nodejs && node -v
# Update to the latest stable node version
RUN npm install -g n --ignore-scripts && n lts
# Install yarn
RUN npm install -g yarnlearned about nodesource through this handy blog However I honestly think running it with like RUN curl -fsSL https://deb.nodesource.com/setup_24.x | bash - && apt-get install -y nodejs && node -vwould work as well but I was just using the oldest Maintenance LTS mentioned on there website https://nodejs.org/en/about/previous-releases also just searched it up and apparently they have this as well which downloads the most recent LTS for nodejs Still not understanidng the pre-commit stuff however. maybe doing a sudo apt install pre-commit in the postCreateCommand.sh would do the trick? but uncertain. |
Beta Was this translation helpful? Give feedback.
-
|
did a PR #11323 that worked for me I'm still confused about the issues I was having with git but Ill figure that out sometime, thanks everyone for your help! I will probably be taking a look at #11279 sometime this weekend, and definitely monday, I may ask for your guys help on pin pointing some stuff out and where I should add stuff. Should I change this to Q&A and then close this discussion and open a new one talking about the barcode stuff? |
Beta Was this translation helpful? Give feedback.
-
|
I did a clean install on a new laptop and it seemed to work fine, I dont know what was going on with that, but its fixed! Thanks again everyone! Will open a new discussion for the barcode plugin issues. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hello again everyone, with how wonderful this software and team is I was going to try and dip my toes in the water to try and see if I could maybe help contribute to bugs/docs. However in getting the dev container set up, everything was going smoothly up until I got this in the VScode terminal
InvenTree database migrations completed # TASK05| done Updating frontend...to which I have sat here for probably 30-40 minutes or so while I have been doing other things, assuming it would resolve itself
it has not
here are the versions I am running as well
Dev Containers VS code v0.442.0
Docker version 29.1.5, build 0e6fee6
VS Code Info
Version: 1.109.2 (user setup)
Commit: 591199df409fbf59b4b52d5ad4ee0470152a9b31
Date: 2026-02-10T20:18:23.520Z
Electron: 39.3.0
ElectronBuildId: 13168319
Chromium: 142.0.7444.265
Node.js: 22.21.1
V8: 14.2.231.22-electron.0
OS: Windows_NT x64 10.0.19045
should I abort the programs and then delete the containers and re-download the repository and try again? or has anyone else run into this issue when setting up there devcontainer? any help would be appreciated!
thanks everyone for your support and hard work!
Beta Was this translation helpful? Give feedback.
All reactions