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

Ubuntu 25.04 script should not autostart the guest #2406

New Issue
Closed
opened 2026-02-05 04:44:27 +03:00 by OVERLORD · 1 comment
OVERLORD commented 2026-02-05 04:44:27 +03:00
Owner
Copy Link

Originally created by @ArchBirdie on GitHub (Jan 28, 2026).

✅ Have you read and understood the above guidelines?

yes

🔎 Did you run the script with verbose mode enabled?

Yes, verbose mode was enabled and the output is included below

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

ubuntu2504-vm.sh

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Ubuntu 24.10

📈 Which Proxmox version are you on?

8.4.14

📝 Provide a clear and concise description of the issue.

After running the script in proxmox console, it says
"Setup Cloud-Init before starting"
However, before this msg is even displayed, the VM is auto-started by the script. Then there is no way to log into the VM unless you turn off the VM to run cloud init.

🔄 Steps to reproduce the issue.

  1. Install the ubuntu 25.04 from helper script with the following command
    bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/ubuntu2504-vm.sh)"
  2. Notice the msg indicating cloud-init should be run BEFORE the vm is started.
  3. Notice the VM is up and running already, and there is no known username or password to login to the VM since cloud init has not been run.

❌ Paste the full error output (if available).

No specific error msg. Just no user available to log in with when the VM autostarts.

🖼️ Additional context (optional).

The point of these scripts is to save the users time. However, it did not save me time when I ran the script, and found the VM up and running. Having not needed to use cloud init in the past, I was not familiar with the process.
I ended up running google searches, deleting the VM, re-installing it with advanced settings and looking to add a password somewhere in the advanced settings.

Anyway, I did notice the cloud init msg on the second time around. But then I was further confused that the VM had autostarted, despite the msg saying you need to run cloud-init before the VM starts.

After shutting off the VM, putting in some cloud init settings and clicking "regenerate image" I was able to power it on and log in. Felt like a lot of guesswork, which is par for the course in the open source world... but we can do better.

An additional helpful thing would be to mention cloud-init on the community scripts page with the ubuntu 25.04 installation instructions.

Originally created by @ArchBirdie on GitHub (Jan 28, 2026). ### ✅ Have you read and understood the above guidelines? yes ### 🔎 Did you run the script with verbose mode enabled? Yes, verbose mode was enabled and the output is included below ### 📜 What is the name of the script you are using? ubuntu2504-vm.sh ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/ubuntu2504-vm.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Ubuntu 24.10 ### 📈 Which Proxmox version are you on? 8.4.14 ### 📝 Provide a clear and concise description of the issue. After running the script in proxmox console, it says "Setup Cloud-Init before starting" However, before this msg is even displayed, the VM is auto-started by the script. Then there is no way to log into the VM unless you turn off the VM to run cloud init. ### 🔄 Steps to reproduce the issue. 1. Install the ubuntu 25.04 from helper script with the following command bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/ubuntu2504-vm.sh)" 2. Notice the msg indicating cloud-init should be run BEFORE the vm is started. 3. Notice the VM is up and running already, and there is no known username or password to login to the VM since cloud init has not been run. ### ❌ Paste the full error output (if available). No specific error msg. Just no user available to log in with when the VM autostarts. ### 🖼️ Additional context (optional). The point of these scripts is to save the users time. However, it did not save me time when I ran the script, and found the VM up and running. Having not needed to use cloud init in the past, I was not familiar with the process. I ended up running google searches, deleting the VM, re-installing it with advanced settings and looking to add a password somewhere in the advanced settings. Anyway, I did notice the cloud init msg on the second time around. But then I was further confused that the VM had autostarted, despite the msg saying you need to run cloud-init before the VM starts. After shutting off the VM, putting in some cloud init settings and clicking "regenerate image" I was able to power it on and log in. Felt like a lot of guesswork, which is par for the course in the open source world... but we can do better. An additional helpful thing would be to mention cloud-init on the community scripts page with the ubuntu 25.04 installation instructions.
OVERLORD added the bug label 2026-02-05 04:44:27 +03:00
OVERLORD commented 2026-02-05 04:44:33 +03:00
Author
Owner
Copy Link

@github-actions[bot] commented on GitHub (Feb 1, 2026):

This issue has been automatically locked. Please open a new issue for related bugs and reference this issue if needed.

@github-actions[bot] commented on GitHub (Feb 1, 2026): This issue has been automatically locked. Please open a new issue for related bugs and reference this issue if needed.
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
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#2406
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?