Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Sign up
Appearance settings

Plex Media Server: Install Stuck on Updating Container OS #4137

Closed Answered by tremor021
qbirdee asked this question in Q&A
Discussion options

Hi,

I have Proxmox up and running, with Home Assistant working fine.

However, I am trying to install Plex Media Server (using the Proxmox VE helper script bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/plex.sh)"), and it keeps getting stuck at "Updating Container OS". I've left it for hours even and its still stuck there. I am installing it to LVM-thin storage if that makes a difference. Thanks in advance for any help!

You must be logged in to vote

Erm... that shouldn't be that slow... You have a serious throtling issue with the repo its downloading from

Replies: 5 comments 5 replies

Comment options

Run the script in verbose mode. Also the command you pasted is not right. you have a extra ), at the end. Should be:
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/plex.sh)"

You must be logged in to vote
0 replies
Comment options

Sorry how do I run in verbose mode? The parenthesis is a typo in my post, sorry. Thanks for the help.
...
On Tue, Apr 29, 2025, 12:55 PM Slaviša Arežina ***@***.***> wrote: Run the script in verbose mode. Also the command you pasted is not right. you have a extra ), at the end. Should be: bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/plex.sh )" — Reply to this email directly, view it on GitHub <https://github.com/orgs/community-scripts/discussions/4137#discussioncomment-12983498>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQFK64NEWQKATHTGLQADZNL236VI3AVCNFSM6AAAAAB4DQJHZCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTEOJYGM2DSOA> . You are receiving this because you authored the thread.Message ID: <community-scripts/ProxmoxVE/repo-discussions/4137/comments/12983498@ github.com>
You must be logged in to vote
0 replies
Comment options

image
It asked you during the install.
Anyway, whatever the error is, its not a script issue. Updating of the container OS is just apt update && apt upgrade -y

You must be logged in to vote
3 replies
Comment options

Ah, yes found the verbose mode.

And turns out, the update is just taking a very, very long time! It's still going, 12 hours later. Probably because I'm trying to use an external USB 3.0 drive for my Plex install. Let's see when it finishes up, thanks for the tip!

Comment options

Erm... that shouldn't be that slow... You have a serious throtling issue with the repo its downloading from

Answer selected by tremor021
Comment options

I'm seeing the same thing. Could a slow apt update && apt upgrade -y be ameliorated by ensuring that my host PVE instance is fully up to date? What does the a new container look like, is it just a mirror of the underlying PVE or does it start from some other well known state?

Comment options

Its finally done. But with this error below. Any concerns, and how to finish off the rest of the script?? Thanks.

Setting up vainfo (2.12.0+ds1-1) ...
 ⠇Setting up libigdfcl1:amd64 (1.0.10840-1) ...
 ⠇Setting up intel-opencl-icd (22.14.22890-1) ...
 ⠙Processing triggers for libc-bin (2.35-0ubuntu3.9) ...
 ⠦Processing triggers for man-db (2.10.2-1) ...
 ✔️ Set Up Hardware Acceleration
 ⠹curl: (35) error:0A000126:SSL routines::unexpected eof while reading
 ⠸
[ERROR] in line 32: exit code 0: while executing command tee /usr/share/keyrings/PlexSign.asc > /dev/null
/dev/fd/63: line 72: SPINNER_PID: unbound variable
You must be logged in to vote
0 replies
Comment options

Updated on another thread, my problem somehow turned out to be a USB storage issue. I switched from a thumb drive to an external SSD, and it worked flawlessly, install took a few minutes. Not sure why it seemingly affected network performance but so it goes. :) Now my problem is no transcoding with my Intel n150 processor. It's a kernel update issue with Proxmox and / or Plex container. I just need to figure out if I can only update Proxmox host or both, and how to fix the LXC container if it's both. :)
...
On Sun, May 11, 2025, 11:40 PM Clay Jensen-Reimann ***@***.***> wrote: I'm seeing the same thing. Could a slow apt update && apt upgrade -y be ameliorated by ensuring that my host PVE instance is fully up to date? What does the a new container look like, is it just a mirror of the underlying PVE or does it start from some other well known state? — Reply to this email directly, view it on GitHub <#4137 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AQFK64IHE2LRZMRVPIESUHL26AJ4JAVCNFSM6AAAAAB4DQJHZCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJRGIZTONI> . You are receiving this because you authored the thread.Message ID: <community-scripts/ProxmoxVE/repo-discussions/4137/comments/13112375@ github.com>
You must be logged in to vote
2 replies
Comment options

Updated on another thread, my problem somehow turned out to be a USB storage issue. I switched from a thumb drive to an external SSD, and it worked flawlessly, install took a few minutes. Not sure why it seemingly affected network performance but so it goes. :) Now my problem is no transcoding with my Intel n150 processor. It's a kernel update issue with Proxmox and / or Plex container. I just need to figure out if I can only update Proxmox host or both, and how to fix the LXC container if it's both. :)
...
On Sun, May 11, 2025, 11:40 PM Clay Jensen-Reimann @.***> wrote: I'm seeing the same thing. Could a slow apt update && apt upgrade -y be ameliorated by ensuring that my host PVE instance is fully up to date? What does the a new container look like, is it just a mirror of the underlying PVE or does it start from some other well known state? — Reply to this email directly, view it on GitHub <#4137 (reply in thread)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AQFK64IHE2LRZMRVPIESUHL26AJ4JAVCNFSM6AAAAAB4DQJHZCVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJRGIZTONI . You are receiving this because you authored the thread.Message ID: <community-scripts/ProxmoxVE/repo-discussions/4137/comments/13112375@ github.com>

Were you able to install on Proxmox with LXC using the N150 graphics card?

Comment options

Yes! It required a kernel update as suspected. Then the LXC worked well with N150 transcoding.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

AltStyle によって変換されたページ (->オリジナル) /