search

babagreensheep / jellyfin-tizen-docker

215 stars 32 forks source link

Update nodejs to version 18 #13

Closed msambartolomeo closed 1 year ago

msambartolomeo commented 1 year ago

jellyfin-tizen now requires node 16+ and it was not building correctly for me with node 14. Updating nodejs fixed the issue (updated to 18 instead of 16 for future-proofing)

msambartolomeo commented 1 year ago

Sorry I didn't specify, my bad. After updating versions I got this error on npm update:

STEP 10/33: RUN npm update
npm ERR! Tracker "idealTree" already exists

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-04-28T01_23_33_890Z-debug-0.log
Error: building at STEP "RUN npm update": while running runtime: exit status 1

After searching about the issue I found here that it seems that after node 15 you need to specify a WORKDIR in a dockerfile before running npm commands, else you get this error. I didn't know which WORKDIR to specify since the jellyfin repos were not cloned yet, so I tried deleting the line and the build then succeeded. I don't really think npm update was necessary in the first place but I may be wrong, and I also didn't find a better workaround than deleting it altogether

skewll commented 1 year ago

Sorry I didn't specify, my bad. After updating versions I got this error on npm update:

STEP 10/33: RUN npm update
npm ERR! Tracker "idealTree" already exists

npm ERR! A complete log of this run can be found in:
npm ERR!     /root/.npm/_logs/2023-04-28T01_23_33_890Z-debug-0.log
Error: building at STEP "RUN npm update": while running runtime: exit status 1

After searching about the issue I found here that it seems that after node 15 you need to specify a WORKDIR in a dockerfile before running npm commands, else you get this error. I didn't know which WORKDIR to specify since the jellyfin repos were not cloned yet, so I tried deleting the line and the build then succeeded. I don't really think npm update was necessary in the first place but I may be wrong, and I also didn't find a better workaround than deleting it altogether

Thanks, changing the node version to 18 and just removing the npm update line all together finally made it work. Ive successfully installed jellyfin on my Samsung TV just. Thanks again to everyone for the info!