kerem commented

Owner

Originally created by @njack21 on GitHub (Nov 10, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9040

✅ Have you read and understood the above guidelines?

yes

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

Docker VM

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

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

⚙️ What settings are you using?

Default Settings
Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 13

📈 Which Proxmox version are you on?

9.0.11

📝 Provide a clear and concise description of the issue.

Installation of Docker VM using script from self hosted did not install Docker in the VM

🔄 Steps to reproduce the issue.

Install Docker VM using script from self hosted site via the Proxmox host shell.
Docker not installed
apt list --installed does not show docker as installed

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

No response

Originally created by @njack21 on GitHub (Nov 10, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9040 ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? Docker VM ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/vm/docker-vm.sh)" ### ⚙️ What settings are you using? - [x] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 13 ### 📈 Which Proxmox version are you on? 9.0.11 ### 📝 Provide a clear and concise description of the issue. Installation of Docker VM using script from self hosted did not install Docker in the VM ### 🔄 Steps to reproduce the issue. 1. Install Docker VM using script from self hosted site via the Proxmox host shell. 2. Docker not installed 3. apt list --installed does not show docker as installed ### ❌ Paste the full error output (if available). <img width="724" height="341" alt="Image" src="https://github.com/user-attachments/assets/381eb42e-72f6-40cb-9869-5bbdca89fd17" /> ### 🖼️ Additional context (optional). _No response_

kerem

2026-02-26 12:50:51 +03:00

closed this issue
added the
bug
label

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 11, 2025):

try this:

bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm.sh)"

@MickLesk commented on GitHub (Nov 11, 2025): try this: bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm.sh)"

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@njack21 commented on GitHub (Nov 11, 2025):

Default login credentials do not work for the VM

@njack21 commented on GitHub (Nov 11, 2025): Default login credentials do not work for the VM

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 11, 2025):

Which Setting? Ive tested all several times today

@MickLesk commented on GitHub (Nov 11, 2025): Which Setting? Ive tested all several times today

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@njack21 commented on GitHub (Nov 11, 2025):

I used defaults. I'll test again.

@njack21 commented on GitHub (Nov 11, 2025): I used defaults. I'll test again.

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 11, 2025):

What? You get 3 or 4 whiptails with this Script. There is no Default.

Post Screenshots - with your 2 or 3 words nobody can help

@MickLesk commented on GitHub (Nov 11, 2025): What? You get 3 or 4 whiptails with this Script. There is no Default. Post Screenshots - with your 2 or 3 words nobody can help

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@njack21 commented on GitHub (Nov 11, 2025):

What?

Use default settings.
Debian 13 (default selection)
Enable Cloud-Init = Yes (default selection)
Install Portainer = Yes (default selection)

I said what I said, I used defaults. (screenshots for your reference)

@njack21 commented on GitHub (Nov 11, 2025): What? 1. Use default settings. 2. Debian 13 (default selection) 3. Enable Cloud-Init = Yes (default selection) 4. Install Portainer = Yes (default selection) I said what I said, I used defaults. (screenshots for your reference) <img width="646" height="510" alt="Image" src="https://github.com/user-attachments/assets/1215d28e-b0f7-4ba8-81cf-bca03740a732" /> <img width="500" height="478" alt="Image" src="https://github.com/user-attachments/assets/647e1e1c-1bcf-4d42-af62-b5968c9e9674" />

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 11, 2025):

The Install is Not completed at your Screenshot?

@MickLesk commented on GitHub (Nov 11, 2025): The Install is Not completed at your Screenshot?

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@njack21 commented on GitHub (Nov 11, 2025):

Screenshot was to demonstrate the default selections chosen. The installation completed without errors. I can run the install again to demonstrate that if need be.

The second screenshot indicates login failure using the default credentials.

Build complete screenshot:

@njack21 commented on GitHub (Nov 11, 2025): Screenshot was to demonstrate the default selections chosen. The installation completed without errors. I can run the install again to demonstrate that if need be. The second screenshot indicates login failure using the default credentials. Build complete screenshot: <img width="692" height="805" alt="Image" src="https://github.com/user-attachments/assets/98499df7-ef57-4023-8095-a0559a51154f" />

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 11, 2025):

And this should Not Work?

Whats your system? Ive deployed yet, Work fine. Its an General function 🤔.

By the way, the live Version too, docker VM Work fine. Installed after 2min after start

@MickLesk commented on GitHub (Nov 11, 2025): And this should Not Work? Whats your system? Ive deployed yet, Work fine. Its an General function 🤔. By the way, the live Version too, docker VM Work fine. Installed after 2min after start

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@njack21 commented on GitHub (Nov 11, 2025):

I think it should work. It does not, unless I am missing something.

System details are in the issue creation. What additional details would you like? I'm happy to provide them.

I'm glad it works from your house. It does not work here. I'm not trying to be a dick, but you saying it works fine isn't helping.

@njack21 commented on GitHub (Nov 11, 2025): I think it should work. It does not, unless I am missing something. System details are in the issue creation. What additional details would you like? I'm happy to provide them. I'm glad it works from your house. It does not work here. I'm not trying to be a dick, but you saying it works fine isn't helping.

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 11, 2025):

Yeah but what should i fix without any something?

I have no Idea atm.

@MickLesk commented on GitHub (Nov 11, 2025): Yeah but what should i fix without any something? I have no Idea atm.

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@njack21 commented on GitHub (Nov 11, 2025):

What additional information can I provide to assist?

Full disclosure, I don't need the Docker VM anymore, I deployed what I needed with another solution, but am happy to assist in diagnosing the issue.

@njack21 commented on GitHub (Nov 11, 2025): What additional information can I provide to assist? Full disclosure, I don't need the Docker VM anymore, I deployed what I needed with another solution, but am happy to assist in diagnosing the issue.

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 11, 2025):

I only can build another Script without any verbose or supressed Outputs, maybe tomorrow

@MickLesk commented on GitHub (Nov 11, 2025): I only can build another Script without any verbose or supressed Outputs, maybe tomorrow

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@ntrance commented on GitHub (Nov 12, 2025):

Docker 29 is the issue; you need to install docker 28.5.2-1

@ntrance commented on GitHub (Nov 12, 2025): Docker 29 is the issue; you need to install docker 28.5.2-1

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@Roma2307 commented on GitHub (Nov 12, 2025):

try this:

bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm.sh)"

I also had problems with Proxmox 9 (VM and lcx docker), but this script worked great. thank you!

Does that mean that the scripts on the Helper website are not up to date?

@Roma2307 commented on GitHub (Nov 12, 2025): > try this: > > bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm.sh)" I also had problems with Proxmox 9 (VM and lcx docker), but this script worked great. thank you! Does that mean that the scripts on the Helper website are not up to date?

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 12, 2025):

no its just an full refactor, with multi os and co. i need testers for this, but nobody in discord response

@MickLesk commented on GitHub (Nov 12, 2025): no its just an full refactor, with multi os and co. i need testers for this, but nobody in discord response

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@Roma2307 commented on GitHub (Nov 12, 2025):

Which Setting? Ive tested all several times today

had the same problem with credentials; this worked for me:

qm set --cipassword "newpassword"

qm cloudinit update
qm reboot

If I install it without cloud-init, I don't need a password at all, only username root.

@Roma2307 commented on GitHub (Nov 12, 2025): > Which Setting? Ive tested all several times today had the same problem with credentials; this worked for me: qm set <vmid> --cipassword "newpassword" qm cloudinit update <vmid> qm reboot <vmid> If I install it without cloud-init, I don't need a password at all, only username root.

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 12, 2025):

and which setting? ^^

@MickLesk commented on GitHub (Nov 12, 2025): and which setting? ^^

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@Roma2307 commented on GitHub (Nov 12, 2025):

and which setting? ^^

Sorry, that statement wasn't entirely correct. I didn't see that the password is displayed in the shell after installation; I thought it was the “root” and “docker” data from the website. The displayed password works.

However, when I install it without Cloud-init using the same settings, no password is set for root (I have no idea if this is intentional).

@Roma2307 commented on GitHub (Nov 12, 2025): > and which setting? ^^ Sorry, that statement wasn't entirely correct. I didn't see that the password is displayed in the shell after installation; I thought it was the “root” and “docker” data from the website. The displayed password works. However, when I install it without Cloud-init using the same settings, no password is set for root (I have no idea if this is intentional). <img width="926" height="970" alt="Image" src="https://github.com/user-attachments/assets/f0eef554-fdce-4f1f-ac65-d08bcb810032" />

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 12, 2025):

so - it work for you?

@MickLesk commented on GitHub (Nov 12, 2025): so - it work for you?

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@Roma2307 commented on GitHub (Nov 12, 2025):

so - it work for you?

yes! :)

@Roma2307 commented on GitHub (Nov 12, 2025): > so - it work for you? yes! :)

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 12, 2025):

@njack21 debug variant:
bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm-debug.sh)"

Post all what you get try debian 13 with and without cloudinit. Wait 3min until all messages are done. then check vm

@MickLesk commented on GitHub (Nov 12, 2025): @njack21 debug variant: bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm-debug.sh)" Post all what you get try debian 13 with and without cloudinit. Wait 3min until all messages are done. then check vm

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@njack21 commented on GitHub (Nov 12, 2025):

@njack21 debug variant: bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm-debug.sh)"

Post all what you get try debian 13 with and without cloudinit. Wait 3min until all messages are done. then check vm

Will test in a bit. On the previous test, I did see the password with cloudinit, but that password did not work either. Will test without cloudinit and update thread.

@njack21 commented on GitHub (Nov 12, 2025): > [@njack21](https://github.com/njack21) debug variant: bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm-debug.sh)" > > Post all what you get try debian 13 with and without cloudinit. Wait 3min until all messages are done. then check vm Will test in a bit. On the previous test, I did see the password with cloudinit, but that password did not work either. Will test without cloudinit and update thread.

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 12, 2025):

how you enter the password? manually? CTRL V ?

Can you make an Video?

@MickLesk commented on GitHub (Nov 12, 2025): how you enter the password? manually? CTRL V ? Can you make an Video?

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@Roma2307 commented on GitHub (Nov 13, 2025):

so - it work for you?

EDIT: Stand down, I've since discovered that it's a problem in the current Portainer release: https://github.com/portainer/portainer/issues/12925#issuecomment-3516549977

Hey Mick, I have another problem and I don't know if it's related to the script. I can't connect to the environment in Portainer under the VM and keep getting the same error. I've reinstalled the VM several times and also deleted Portainer and reinstalled it manually, but the error keeps coming back. Do you have any idea what the cause could be?

@Roma2307 commented on GitHub (Nov 13, 2025): > so - it work for you? EDIT: **Stand down, I've since discovered that it's a problem in the current Portainer release: https://github.com/portainer/portainer/issues/12925#issuecomment-3516549977** Hey Mick, I have another problem and I don't know if it's related to the script. I can't connect to the environment in Portainer under the VM and keep getting the same error. I've reinstalled the VM several times and also deleted Portainer and reinstalled it manually, but the error keeps coming back. Do you have any idea what the cause could be? <img width="1379" height="610" alt="Image" src="https://github.com/user-attachments/assets/e687cf1f-834a-44da-9037-6869e90390e8" />

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@MickLesk commented on GitHub (Nov 13, 2025):

Upstream issue. Waiting.

@MickLesk commented on GitHub (Nov 13, 2025): Upstream issue. Waiting.

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

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

@njack21 any feedback or progress?

@MickLesk commented on GitHub (Nov 18, 2025): @njack21 any feedback or progress?

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@Onoitsu2 commented on GitHub (Nov 23, 2025):

2 ways to potentially workaround that upstream issue related to docker 29 shown at
https://www.reddit.com/r/portainer/comments/1oumupa/comment/none9ai/
and
this comment and then also near the bottom
https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4849#issuecomment-3495904254

@Onoitsu2 commented on GitHub (Nov 23, 2025): 2 ways to potentially workaround that upstream issue related to docker 29 shown at https://www.reddit.com/r/portainer/comments/1oumupa/comment/none9ai/ and this comment and then also near the bottom https://github.com/NginxProxyManager/nginx-proxy-manager/issues/4849#issuecomment-3495904254

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@BrianBonnell commented on GitHub (Dec 18, 2025):

Any updates on this script? I'm having issues with the script completes successfully, but when you go to run ANY docker command you get command not found. Looking though, the OS gets installed however docker does not. Oddly this same script worked just find on my Dell PowerEdge R430, but keeps failing out like this on my HPE Microserver Gen 10. Regardless of version of Debian I use on any script on this HPE it fails the LXC Docker script works just fine on both. Not sure if this helps or adds to the issue.

I see alot of similar errors like below for both Debian 12 and 13 - just the versions referenced in the errors is different, I thought it might be a DNS issue, but these hostnames in both OS version do resolve if you go to them directly.

I am having no issues resolving deb.debian.org.

Hope this helps in some way....

Patiently waiting......

Get:3 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B]
Ign:2 https://deb.debian.org/debian bookworm InRelease
Ign:4 https://deb.debian.org/debian bookworm-updates InRelease
Ign:5 https://deb.debian.org/debian bookworm-backports InRelease
Ign:6 https://deb.debian.org/debian-security bookworm-security InRelease
Ign:2 https://deb.debian.org/debian bookworm InRelease
Ign:4 https://deb.debian.org/debian bookworm-updates InRelease
Ign:5 https://deb.debian.org/debian bookworm-backports InRelease
Ign:6 https://deb.debian.org/debian-security bookworm-security InRelease
Ign:2 https://deb.debian.org/debian bookworm InRelease
Ign:4 https://deb.debian.org/debian bookworm-updates InRelease
Ign:5 https://deb.debian.org/debian bookworm-backports InRelease
Ign:6 https://deb.debian.org/debian-security bookworm-security InRelease
Err:2 https://deb.debian.org/debian bookworm InRelease
Temporary failure resolving 'deb.debian.org'
Err:4 https://deb.debian.org/debian bookworm-updates InRelease
Temporary failure resolving 'deb.debian.org'
Err:5 https://deb.debian.org/debian bookworm-backports InRelease
Temporary failure resolving 'deb.debian.org'
Err:6 https://deb.debian.org/debian-security bookworm-security InRelease
Temporary failure resolving 'deb.debian.org'
Reading package lists...
W: Failed to fetch mirror+file:/etc/apt/mirrors/debian.list/dists/bookworm/InRelease Temporary failure resolving 'deb.debian.org'
W: Failed to fetch mirror+file:/etc/apt/mirrors/debian.list/dists/bookworm-updates/InRelease Temporary failure resolving 'deb.debian.org'
W: Failed to fetch mirror+file:/etc/apt/mirrors/debian.list/dists/bookworm-backports/InRelease Temporary failure resolving 'deb.debian.org'
W: Failed to fetch mirror+file:/etc/apt/mirrors/debian-security.list/dists/bookworm-security/InRelease Temporary failure resolving 'deb.debian.org'
W: Some index files failed to download. They have been ignored, or old ones used instead.
Reading package lists...
Building dependency tree...
Reading state information...
Package gnupg is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source

E: Unable to locate package qemu-guest-agent
E: Package 'gnupg' has no installation candidate
E: Unable to locate package software-properties-common
virt-customize: error:
export DEBIAN_FRONTEND=noninteractive
apt_opts='-q -y -o Dpkg::Options::=--force-confnew'
apt-get $apt_opts update
apt-get $apt_opts install 'qemu-guest-agent' 'apt-transport-https'
'ca-certificates' 'curl' 'gnupg' 'software-properties-common' 'lsb-release'
: command exited with an error

If reporting bugs, run virt-customize with debugging enabled and include
the complete output:

virt-customize -v -x [...]

Doing some more digging I found these errors in cat /var/log/install-docker.log

[Thu Dec 18 10:13:35 UTC 2025] Installing Docker

Executing docker install script, commit: 8b33a64d28ec86a1121623f1d349801b48f2837b

sh -c apt-get -qq update >/dev/null
W: OpenPGP signature verification failed: https://deb.debian.org/debian-security trixie-security InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2025-12-18T13:33:01Z Verifying signature: Not live until 2025-12-18T13:33:01Z
E: The repository 'mirror+file:/etc/apt/mirrors/debian-security.list trixie-security InRelease' is not signed.
Failed to enable unit: Unit docker.service does not exist
Failed to start docker.service: Unit docker.service not found.
[Thu Dec 18 15:13:49 UTC 2025] Docker installation completed successfully
l.sh: line 5: docker: command not found
[Thu Dec 18 15:13:49 UTC 2025] Portainer installed
root@dockervm2b:~# docker ps

@BrianBonnell commented on GitHub (Dec 18, 2025): Any updates on this script? I'm having issues with the script completes successfully, but when you go to run ANY docker command you get command not found. Looking though, the OS gets installed however docker does not. Oddly this same script worked just find on my Dell PowerEdge R430, but keeps failing out like this on my HPE Microserver Gen 10. Regardless of version of Debian I use on any script on this HPE it fails the LXC Docker script works just fine on both. Not sure if this helps or adds to the issue. I see alot of similar errors like below for both Debian 12 and 13 - just the versions referenced in the errors is different, I thought it might be a DNS issue, but these hostnames in both OS version do resolve if you go to them directly. I am having no issues resolving deb.debian.org. Hope this helps in some way.... Patiently waiting...... Get:3 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B] Ign:2 https://deb.debian.org/debian bookworm InRelease Ign:4 https://deb.debian.org/debian bookworm-updates InRelease Ign:5 https://deb.debian.org/debian bookworm-backports InRelease Ign:6 https://deb.debian.org/debian-security bookworm-security InRelease Ign:2 https://deb.debian.org/debian bookworm InRelease Ign:4 https://deb.debian.org/debian bookworm-updates InRelease Ign:5 https://deb.debian.org/debian bookworm-backports InRelease Ign:6 https://deb.debian.org/debian-security bookworm-security InRelease Ign:2 https://deb.debian.org/debian bookworm InRelease Ign:4 https://deb.debian.org/debian bookworm-updates InRelease Ign:5 https://deb.debian.org/debian bookworm-backports InRelease Ign:6 https://deb.debian.org/debian-security bookworm-security InRelease Err:2 https://deb.debian.org/debian bookworm InRelease Temporary failure resolving 'deb.debian.org' Err:4 https://deb.debian.org/debian bookworm-updates InRelease Temporary failure resolving 'deb.debian.org' Err:5 https://deb.debian.org/debian bookworm-backports InRelease Temporary failure resolving 'deb.debian.org' Err:6 https://deb.debian.org/debian-security bookworm-security InRelease Temporary failure resolving 'deb.debian.org' Reading package lists... W: Failed to fetch mirror+file:/etc/apt/mirrors/debian.list/dists/bookworm/InRelease Temporary failure resolving 'deb.debian.org' W: Failed to fetch mirror+file:/etc/apt/mirrors/debian.list/dists/bookworm-updates/InRelease Temporary failure resolving 'deb.debian.org' W: Failed to fetch mirror+file:/etc/apt/mirrors/debian.list/dists/bookworm-backports/InRelease Temporary failure resolving 'deb.debian.org' W: Failed to fetch mirror+file:/etc/apt/mirrors/debian-security.list/dists/bookworm-security/InRelease Temporary failure resolving 'deb.debian.org' W: Some index files failed to download. They have been ignored, or old ones used instead. Reading package lists... Building dependency tree... Reading state information... Package gnupg is not available, but is referred to by another package. This may mean that the package is missing, has been obsoleted, or is only available from another source E: Unable to locate package qemu-guest-agent E: Package 'gnupg' has no installation candidate E: Unable to locate package software-properties-common virt-customize: error: export DEBIAN_FRONTEND=noninteractive apt_opts='-q -y -o Dpkg::Options::=--force-confnew' apt-get $apt_opts update apt-get $apt_opts install 'qemu-guest-agent' 'apt-transport-https' 'ca-certificates' 'curl' 'gnupg' 'software-properties-common' 'lsb-release' : command exited with an error If reporting bugs, run virt-customize with debugging enabled and include the complete output: virt-customize -v -x [...] Doing some more digging I found these errors in cat /var/log/install-docker.log [Thu Dec 18 10:13:35 UTC 2025] Installing Docker # Executing docker install script, commit: 8b33a64d28ec86a1121623f1d349801b48f2837b + sh -c apt-get -qq update >/dev/null W: OpenPGP signature verification failed: https://deb.debian.org/debian-security trixie-security InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Verifying signature: Not live until 2025-12-18T13:33:01Z Verifying signature: Not live until 2025-12-18T13:33:01Z E: The repository 'mirror+file:/etc/apt/mirrors/debian-security.list trixie-security InRelease' is not signed. Failed to enable unit: Unit docker.service does not exist Failed to start docker.service: Unit docker.service not found. [Thu Dec 18 15:13:49 UTC 2025] Docker installation completed successfully l.sh: line 5: docker: command not found [Thu Dec 18 15:13:49 UTC 2025] Portainer installed root@dockervm2b:~# docker ps

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

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

there is an script above and i dont get any feedback

@MickLesk commented on GitHub (Dec 18, 2025): there is an script above and i dont get any feedback

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

@BrianBonnell commented on GitHub (Dec 18, 2025):

there is an script above and i dont get any feedback:

I ran the script bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm.sh)"

Not sure if this was what script your referring to, but below is how I fixed my issue.

Ok I was able to manage getting both docker installed and portainer.....the first time boot fails, HOWEVER in root directory there is two scripts:

root@dockervm2b:~# ls
install-docker.sh portainer-install.sh

If you just run again the install-docker script it installs docker correctly, and portainer comes up as expected.
root@dockervm2b:~# ./install-docker.sh

root@dockervm2b:~# docker ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
12c29f6f2cb6 portainer/portainer-ce:latest "/portainer" 42 seconds ago Up 37 seconds 0.0.0.0:9000->9000/tcp, [::]:9000->9000/tcp, 8000/tcp, 0.0.0.0:9443->9443/tcp, [::]:9443->9443/tcp portainer

@BrianBonnell commented on GitHub (Dec 18, 2025): > there is an script above and i dont get any feedback: I ran the script **bash -c "$(curl -fsSL https://git.community-scripts.org/community-scripts/ProxmoxVED/raw/branch/main/vm/docker-vm.sh)"** Not sure if this was what script your referring to, but below is how I fixed my issue. Ok I was able to manage getting both docker installed and portainer.....the first time boot fails, HOWEVER in root directory there is two scripts: root@dockervm2b:~# ls **install-docker.sh** portainer-install.sh If you just run again the install-docker script it installs docker correctly, and portainer comes up as expected. root@dockervm2b:~# ./install-docker.sh root@dockervm2b:~# docker ps CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES 12c29f6f2cb6 portainer/portainer-ce:latest "/portainer" 42 seconds ago Up 37 seconds 0.0.0.0:9000->9000/tcp, [::]:9000->9000/tcp, 8000/tcp, 0.0.0.0:9443->9443/tcp, [::]:9443->9443/tcp portainer

kerem commented

2026-02-26 12:50:52 +03:00

Author

Owner

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

That need 10min after Boot

@MickLesk commented on GitHub (Dec 18, 2025): That need 10min after Boot

kerem referenced this issue

2026-02-26 13:33:39 +03:00

[PR #2011] [MERGED] Fix Tianji: Add heap-space value for nodejs #3476

Rows
Columns

[GH-ISSUE #9040] Docker VM does not install Docker #1973

✅ Have you read and understood the above guidelines?

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

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

⚙️ What settings are you using?

🖥️ Which Linux distribution are you using?

📈 Which Proxmox version are you on?

📝 Provide a clear and concise description of the issue.

🔄 Steps to reproduce the issue.

❌ Paste the full error output (if available).

🖼️ Additional context (optional).

Executing docker install script, commit: 8b33a64d28ec86a1121623f1d349801b48f2837b