SVI/ProxmoxVE
1
0
Fork 0
mirror of https://github.com/community-scripts/ProxmoxVE.git synced 2026-03-31 06:34:17 -04:00
Code Issues 2.6k Packages Projects Releases 10 Wiki Activity

Zipline fails to upgrade to V4 via helper script #558

New Issue
Closed
opened 2025-11-20 04:50:10 -05:00 by saavagebueno · 8 comments
saavagebueno commented 2025-11-20 04:50:10 -05:00
Owner
Copy Link

Originally created by @meemkade on GitHub (Feb 18, 2025).

✅ Have you read and understood the above guidelines?

yes

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

Zipline LXC

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/zipline.sh)"

📝 Provide a clear and concise description of the issue.

I was on V3 of zipline, and I wanted to upgrade to V4. I executed the command inside of the LXC and started the update, with it then saying that it updated successfully.

Image
(ignore the broadcast announcement)

Despite it saying it was successful, when I try to visit the webpage, it dosen't work, and viewing zipline via service shows this:

Image

Ive seen 2 issues mentioning zipline failing to install about 20 hours ago with them being closed, but despite that my update still fails, forcing me to stay on V3.

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

Step 1: Have an existing Zipline LXC on V3
Step 2: Enter said LXC via lxc-attach or the proxmox console
Step 3: Run the helper script thats meant to update the LXC
Step 4: Say yes to the update confirmation
Step 5: Let the LXC update
Step 6: Attempt to visit the LXC's webpage after it is done updating, observe error

❌ Paste the full error output (if available).

✔️ No update required. Zipline is already at 4.0.0
root@zipline:/opt/zipline# service zipline status
× zipline.service - Zipline Service
Loaded: loaded (/etc/systemd/system/zipline.service; enabled; preset: enabled)
Active: failed (Result: exit-code) since Tue 2025-02-18 12:10:11 EST; 5min ago
Duration: 519ms
Process: 404 ExecStart=/usr/bin/yarn start (code=exited, status=1/FAILURE)
Main PID: 404 (code=exited, status=1/FAILURE)
CPU: 517ms

Feb 18 12:10:11 zipline systemd[1]: zipline.service: Scheduled restart job, restart counter is at 5.
Feb 18 12:10:11 zipline systemd[1]: Stopped zipline.service - Zipline Service.
Feb 18 12:10:11 zipline systemd[1]: zipline.service: Start request repeated too quickly.
Feb 18 12:10:11 zipline systemd[1]: zipline.service: Failed with result 'exit-code'.
Feb 18 12:10:11 zipline systemd[1]: Failed to start zipline.service - Zipline Service.
root@zipline:/opt/zipline# ^C
root@zipline:/opt/zipline#

🖼️ Additional context (optional).

No response

Originally created by @meemkade on GitHub (Feb 18, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Zipline LXC ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/zipline.sh)" ### 📝 Provide a clear and concise description of the issue. I was on V3 of zipline, and I wanted to upgrade to V4. I executed the command inside of the LXC and started the update, with it then saying that it updated successfully. ![Image](https://github.com/user-attachments/assets/c73cb163-1979-45af-80f6-27121a326acd) (ignore the broadcast announcement) Despite it saying it was successful, when I try to visit the webpage, it dosen't work, and viewing zipline via service shows this: ![Image](https://github.com/user-attachments/assets/eb5a880c-6d53-4d4e-bf03-a4c0aa96b0b2) Ive seen 2 issues mentioning zipline failing to install about 20 hours ago with them being closed, but despite that my update still fails, forcing me to stay on V3. ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. Step 1: Have an existing Zipline LXC on V3 Step 2: Enter said LXC via lxc-attach or the proxmox console Step 3: Run the helper script thats meant to update the LXC Step 4: Say yes to the update confirmation Step 5: Let the LXC update Step 6: Attempt to visit the LXC's webpage after it is done updating, observe error ### ❌ Paste the full error output (if available). ✔️ No update required. Zipline is already at 4.0.0 root@zipline:/opt/zipline# service zipline status × zipline.service - Zipline Service Loaded: loaded (/etc/systemd/system/zipline.service; enabled; preset: enabled) Active: failed (Result: exit-code) since Tue 2025-02-18 12:10:11 EST; 5min ago Duration: 519ms Process: 404 ExecStart=/usr/bin/yarn start (code=exited, status=1/FAILURE) Main PID: 404 (code=exited, status=1/FAILURE) CPU: 517ms Feb 18 12:10:11 zipline systemd[1]: zipline.service: Scheduled restart job, restart counter is at 5. Feb 18 12:10:11 zipline systemd[1]: Stopped zipline.service - Zipline Service. Feb 18 12:10:11 zipline systemd[1]: zipline.service: Start request repeated too quickly. Feb 18 12:10:11 zipline systemd[1]: zipline.service: Failed with result 'exit-code'. Feb 18 12:10:11 zipline systemd[1]: Failed to start zipline.service - Zipline Service. root@zipline:/opt/zipline# ^C root@zipline:/opt/zipline# ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 04:50:10 -05:00
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 18, 2025):

There is no Update from v3 possible. Read Changelog & Look at migration from zipline Site

@MickLesk commented on GitHub (Feb 18, 2025): There is no Update from v3 possible. Read Changelog & Look at migration from zipline Site
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@meemkade commented on GitHub (Feb 18, 2025):

Wheres the changelog? Also I initally tried the migration on the zipline docs but gave up because docker isnt installed which is what I need to upgrade to V4 (yet the lxc is missing it)

Image
Im pretty sure this is the issue

@meemkade commented on GitHub (Feb 18, 2025): Wheres the changelog? Also I initally tried the migration on the zipline docs but gave up because docker isnt installed which is what I need to upgrade to V4 (yet the lxc is missing it) ![Image](https://github.com/user-attachments/assets/9075d898-4e16-436e-9640-11fbf0fac2fe) Im pretty sure this is the issue
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@meemkade commented on GitHub (Feb 18, 2025):

Also, why is this on the website then, and why does the script attempt to update to V4 in the first place if it isnt possible? Seems misleading and it'll just brick peoples installations when it tries to

Image

@meemkade commented on GitHub (Feb 18, 2025): Also, why is this on the website then, and why does the script attempt to update to V4 in the first place if it isnt possible? Seems misleading and it'll just brick peoples installations when it tries to ![Image](https://github.com/user-attachments/assets/441f277f-7009-4afd-bee0-4684961ba5f2)
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 18, 2025):

Create an new LXC. We really cant check which Version is installed and the installs of zipline are very low

@MickLesk commented on GitHub (Feb 18, 2025): Create an new LXC. We really cant check which Version is installed and the installs of zipline are very low
saavagebueno commented 2025-11-20 04:50:11 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 18, 2025):

You can do an Git diff and Change your Service File maybe. Checkout our Changelog and the PR for this.

@MickLesk commented on GitHub (Feb 18, 2025): You can do an Git diff and Change your Service File maybe. Checkout our Changelog and the PR for this.
saavagebueno commented 2025-11-20 04:50:12 -05:00
Author
Owner
Copy Link

@meemkade commented on GitHub (Feb 18, 2025):

If I make a new LXC, how should I go about transferring data from the V3 to the V4? I have links that I cant afford to lose if I have to delete the V3

@meemkade commented on GitHub (Feb 18, 2025): If I make a new LXC, how should I go about transferring data from the V3 to the V4? I have links that I cant afford to lose if I have to delete the V3
saavagebueno commented 2025-11-20 04:50:12 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 18, 2025):

Idk, im Not the maintainer of zipline. We only provide the Scripts. Maybe you can check the PR from me and do manually the Same for Migration. Because the maintainer remove .env and rename Environment Variables, and use pnpm instead yarn

Thats to much to prevent in our Scripts

@MickLesk commented on GitHub (Feb 18, 2025): Idk, im Not the maintainer of zipline. We only provide the Scripts. Maybe you can check the PR from me and do manually the Same for Migration. Because the maintainer remove .env and rename Environment Variables, and use pnpm instead yarn Thats to much to prevent in our Scripts
saavagebueno commented 2025-11-20 04:50:12 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Feb 18, 2025):

here take a look:
https://github.com/community-scripts/ProxmoxVE/pull/2455/files

@MickLesk commented on GitHub (Feb 18, 2025): here take a look: https://github.com/community-scripts/ProxmoxVE/pull/2455/files
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
🛑 Failure to comply with the guidelines
breaking change
bug
bug
bugfix
deferred
delete script
dependencies
enhancement
external
feature
github
help wanted
Implemented in VED waiting push to Main
in project pipeline
invalid
investigation
json
maintenance
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
No Label bug
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
saavagebueno
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: SVI/ProxmoxVE#558
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?