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

PVE 9.x.x Docker VM install issue #1783

New Issue
Closed
opened 2025-11-20 05:17:20 -05:00 by saavagebueno · 12 comments
saavagebueno commented 2025-11-20 05:17:20 -05:00
Owner
Copy Link

Originally created by @jffluis on GitHub (Aug 25, 2025).

✅ Have you read and understood the above guidelines?

yes

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

DockerVM

📂 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 12

📝 Provide a clear and concise description of the issue.

Tested in 2 PVE 9 envs end with the same error.
Saw an issue like this 2 weeks ago that got closed and got told to the user that were caused by a network issue but it dont see it. VM gets IP without a problem.

🔄 Steps to reproduce the issue.

  • Step 1: Run the Docker VM in host and get the script error

❌ Paste the full error output (if available).

Adding Docker and Docker Compose Plugin to Debian 12 Qcow2 Disk Image Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B]
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 [...]

🖼️ Additional context (optional).

No response

Originally created by @jffluis on GitHub (Aug 25, 2025). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? DockerVM ### 📂 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 - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📝 Provide a clear and concise description of the issue. Tested in 2 PVE 9 envs end with the same error. Saw an issue like this 2 weeks ago that got closed and got told to the user that were caused by a network issue but it dont see it. VM gets IP without a problem. ### 🔄 Steps to reproduce the issue. - Step 1: Run the Docker VM in host and get the script error ### ❌ Paste the full error output (if available). ``` Adding Docker and Docker Compose Plugin to Debian 12 Qcow2 Disk Image Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B] 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 [...] ``` ### 🖼️ Additional context (optional). _No response_
saavagebueno added the bug label 2025-11-20 05:17:20 -05:00
saavagebueno commented 2025-11-20 05:17:21 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Aug 25, 2025):

Temporary failure resolving 'deb.debian.org'

check your network / Adblock / PiHole / DNS / DHCP / Tailscale

@MickLesk commented on GitHub (Aug 25, 2025): Temporary failure resolving 'deb.debian.org' check your network / Adblock / PiHole / DNS / DHCP / Tailscale
saavagebueno commented 2025-11-20 05:17:21 -05:00
Author
Owner
Copy Link

@jffluis commented on GitHub (Aug 25, 2025):

Thank for your fast response. I tried that and nothing one PVE has def adguard. Removed that and just left CF and google DNS and still the same error.

I can ping and traceroute that domain in host without a problem.

The second PVE 9 env is in a DC doesn't have any custom dns servers. Just using CF and google DNS.
Also adding that I've installed a Docker VM in 2nd env when it was in PVE 8 and after update to 9 this error started without any config/DNS change.

qcow file domain resolves without an issue why it fails after that?

✔️  https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-nocloud-amd64.qcow2
✔️  Downloaded debian-12-nocloud-amd64.qcow2

Inside the unconfigured Vm i got Ip and i can ping debian servers. Very very strange issue.

Tested Docker LXC Script and works without any issue..

@jffluis commented on GitHub (Aug 25, 2025): Thank for your fast response. I tried that and nothing one PVE has def adguard. Removed that and just left CF and google DNS and still the same error. I can ping and traceroute that domain in host without a problem. The second PVE 9 env is in a DC doesn't have any custom dns servers. Just using CF and google DNS. \ Also adding that I've installed a Docker VM in 2nd env when it was in PVE 8 and after update to 9 this error started without any config/DNS change. qcow file domain resolves without an issue why it fails after that? ``` ✔️ https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-nocloud-amd64.qcow2 ✔️ Downloaded debian-12-nocloud-amd64.qcow2 ``` Inside the unconfigured Vm i got Ip and i can ping debian servers. Very very strange issue. Tested Docker LXC Script and works without any issue..
saavagebueno commented 2025-11-20 05:17:21 -05:00
Author
Owner
Copy Link

@Popcorncandy09 commented on GitHub (Sep 2, 2025):

Same issue for me:

____             __                _    ____  ___

/ __ ____ / / _____ | | / / |/ /
/ / / / __ / / /// _ / / | | / / /|/ /
/ // / // / // ,< / / / | |/ / / / /
//_/_//||_// |// //

⚙️ Using Default Settings
🆔 Virtual Machine ID: 119
📦 Machine Type: i440fx
💾 Disk Size: 10G
💾 Disk Cache: None
🏠 Hostname: docker
🖥️ CPU Model: KVM64
🧠 CPU Cores: 2
🛠️ RAM Size: 4096
🌉 Bridge: vmbr0
🔗 MAC Address:
🏷️ VLAN: Default
⚙️ Interface MTU Size: Default
🌐 Start VM when completed: yes
🚀 Creating a Docker VM using the above default settings
✔️ Using local for Storage Location.
✔️ Virtual Machine ID is 119.
✔️ https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-nocloud-amd64.qcow2
✔️ Downloaded debian-12-nocloud-amd64.qcow2
✔️ Installed libguestfs-tools successfully
Adding Docker and Docker Compose Plugin to Debian 12 Qcow2 Disk Image Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B]
Get:5 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B]
Ign:2 https://deb.debian.org/debian bookworm InRelease
Ign:3 https://deb.debian.org/debian bookworm-updates InRelease
Ign:4 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:3 https://deb.debian.org/debian bookworm-updates InRelease
Ign:4 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:3 https://deb.debian.org/debian bookworm-updates InRelease
Ign:4 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:3 https://deb.debian.org/debian bookworm-updates InRelease
Temporary failure resolving 'deb.debian.org'
Err:4 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 [...]
✔️ Added Docker and Docker Compose Plugin to Debian 12 Qcow2 Disk Image successfully
✔️ Expanded image to full size
Creating a Docker VM shrinking disks is not supported
✔️ Created a Docker VM (docker)
✔️ Started Docker VM
✔️ Completed Successfully!

@Popcorncandy09 commented on GitHub (Sep 2, 2025): Same issue for me: ____ __ _ ____ ___ / __ \____ _____/ /_____ _____ | | / / |/ / / / / / __ \/ ___/ //_/ _ \/ ___/ | | / / /|_/ / / /_/ / /_/ / /__/ ,< / __/ / | |/ / / / / /_____/\____/\___/_/|_|\___/_/ |___/_/ /_/ ⚙️ Using Default Settings 🆔 Virtual Machine ID: 119 📦 Machine Type: i440fx 💾 Disk Size: 10G 💾 Disk Cache: None 🏠 Hostname: docker 🖥️ CPU Model: KVM64 🧠 CPU Cores: 2 🛠️ RAM Size: 4096 🌉 Bridge: vmbr0 🔗 MAC Address: 🏷️ VLAN: Default ⚙️ Interface MTU Size: Default 🌐 Start VM when completed: yes 🚀 Creating a Docker VM using the above default settings ✔️ Using local for Storage Location. ✔️ Virtual Machine ID is 119. ✔️ https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-nocloud-amd64.qcow2 ✔️ Downloaded debian-12-nocloud-amd64.qcow2 ✔️ Installed libguestfs-tools successfully Adding Docker and Docker Compose Plugin to Debian 12 Qcow2 Disk Image Get:1 file:/etc/apt/mirrors/debian.list Mirrorlist [30 B] Get:5 file:/etc/apt/mirrors/debian-security.list Mirrorlist [39 B] Ign:2 https://deb.debian.org/debian bookworm InRelease Ign:3 https://deb.debian.org/debian bookworm-updates InRelease Ign:4 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:3 https://deb.debian.org/debian bookworm-updates InRelease Ign:4 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:3 https://deb.debian.org/debian bookworm-updates InRelease Ign:4 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:3 https://deb.debian.org/debian bookworm-updates InRelease Temporary failure resolving 'deb.debian.org' Err:4 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 [...] ✔️ Added Docker and Docker Compose Plugin to Debian 12 Qcow2 Disk Image successfully ✔️ Expanded image to full size Creating a Docker VM shrinking disks is not supported ✔️ Created a Docker VM (docker) ✔️ Started Docker VM ✔️ Completed Successfully!
saavagebueno commented 2025-11-20 05:17:21 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 2, 2025):

Temporary failure resolving 'deb.debian.org

@MickLesk commented on GitHub (Sep 2, 2025): Temporary failure resolving 'deb.debian.org
saavagebueno commented 2025-11-20 05:17:21 -05:00
Author
Owner
Copy Link

@jffluis commented on GitHub (Sep 2, 2025):

But have you tried the script in PVE v9? That error, to me, seems to be very misleading. I got internet connection at the VM and DNS are working properly. I only get problem with that specific script.

@jffluis commented on GitHub (Sep 2, 2025): But have you tried the script in PVE v9? That error, to me, seems to be very misleading. I got internet connection at the VM and DNS are working properly. I only get problem with that specific script.
saavagebueno commented 2025-11-20 05:17:22 -05:00
Author
Owner
Copy Link

@Rebem13 commented on GitHub (Sep 5, 2025):

I'm also having this issue with the Docker VM script on an upgraded 8 => 9 PVE server. I can name resolve deb.debian.org from the host.

@Rebem13 commented on GitHub (Sep 5, 2025): I'm also having this issue with the Docker VM script on an upgraded 8 => 9 PVE server. I can name resolve deb.debian.org from the host.
saavagebueno commented 2025-11-20 05:17:22 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Sep 5, 2025):

yeah, its already in fixing, at ProxmoxVED. But its not so easy in PVE9 (virt-customize doesnt work fine). You can try the same Script with "ProxmoxVED" instead of "ProxmoxVE". (But you need to wait 5-10min after install for the post setup) - its not perfect at the moment, but im very busy this week :(

@MickLesk commented on GitHub (Sep 5, 2025): yeah, its already in fixing, at ProxmoxVED. But its not so easy in PVE9 (virt-customize doesnt work fine). You can try the same Script with "ProxmoxVED" instead of "ProxmoxVE". (But you need to wait 5-10min after install for the post setup) - its not perfect at the moment, but im very busy this week :(
saavagebueno commented 2025-11-20 05:17:22 -05:00
Author
Owner
Copy Link

@michelroegl-brunner commented on GitHub (Oct 13, 2025):

I got similar errors (unable to resolve cloud.debian.org) in a fresh Trixie install of VE 9.0.10. Eventually that part succeeded after several retries, but then it tried to install squid from the wrong (enterprise) server even though I'm running from the free one and the enterprise one was commented out by post-install. I'm installing onto a Ceph RBD.:

    ____             __                _    ____  ___
   / __ \____  _____/ /_____  _____   | |  / /  |/  /
  / / / / __ \/ ___/ //_/ _ \/ ___/   | | / / /|_/ /
 / /_/ / /_/ / /__/ ,< /  __/ /       | |/ / /  / /
/_____/\____/\___/_/|_|\___/_/        |___/_/  /_/

  ⚙️  Using Default Settings
  🆔  Virtual Machine ID: 103
  📦  Machine Type: i440fx
  💾  Disk Size: 10G
  💾  Disk Cache: None
  🏠  Hostname: docker
  🖥️  CPU Model: KVM64
  🧠  CPU Cores: 2
  🛠️  RAM Size: 4096
  🌉  Bridge: vmbr0
  🔗  MAC Address: 02:B9:0B:BA:18:05
  🏷️  VLAN: Default
  ⚙️  Interface MTU Size: Default
  🌐  Start VM when completed: yes
  🚀  Creating a Docker VM using the above default settings
  ✔️  Using rbd-vmstore for Storage Location.
  ✔️  Virtual Machine ID is 103.
  ✔️  https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-nocloud-amd64.qcow2
  ✔️  Downloaded debian-12-nocloud-amd64.qcow2
   Installing Pre-Requisite libguestfs-tools onto Host E: Failed to fetch https://enterprise.proxmox.com/debian/ceph-squid/dists/trixie/InRelease  401  Unauthorized [IP: 66.70.154.82 443]
E: The repository 'https://enterprise.proxmox.com/debian/ceph-squid trixie InRelease' is not signed.

[ERROR] in line 498: exit code 100: while executing command apt-get -qq update > /dev/null

root@pve01:~#

You have the enterprise repository enabled, this only works when you have a subscription. this is not related to the issue at hand: `nstalling Pre-Requisite libguestfs-tools onto Host E: Failed to fetch https://enterprise.proxmox.com/debian/ceph-squid/dists/trixie/InRelease 401 Unauthorized [IP: 66.70.154.82 443]

E: The repository 'https://enterprise.proxmox.com/debian/ceph-squid trixie InRelease' is not signed.`

@michelroegl-brunner commented on GitHub (Oct 13, 2025): > I got similar errors (unable to resolve cloud.debian.org) in a fresh Trixie install of VE 9.0.10. Eventually that part succeeded after several retries, but then it tried to install squid from the wrong (enterprise) server even though I'm running from the free one and the enterprise one was commented out by post-install. I'm installing onto a Ceph RBD.: > > ``` > ____ __ _ ____ ___ > / __ \____ _____/ /_____ _____ | | / / |/ / > / / / / __ \/ ___/ //_/ _ \/ ___/ | | / / /|_/ / > / /_/ / /_/ / /__/ ,< / __/ / | |/ / / / / > /_____/\____/\___/_/|_|\___/_/ |___/_/ /_/ > > ⚙️ Using Default Settings > 🆔 Virtual Machine ID: 103 > 📦 Machine Type: i440fx > 💾 Disk Size: 10G > 💾 Disk Cache: None > 🏠 Hostname: docker > 🖥️ CPU Model: KVM64 > 🧠 CPU Cores: 2 > 🛠️ RAM Size: 4096 > 🌉 Bridge: vmbr0 > 🔗 MAC Address: 02:B9:0B:BA:18:05 > 🏷️ VLAN: Default > ⚙️ Interface MTU Size: Default > 🌐 Start VM when completed: yes > 🚀 Creating a Docker VM using the above default settings > ✔️ Using rbd-vmstore for Storage Location. > ✔️ Virtual Machine ID is 103. > ✔️ https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-nocloud-amd64.qcow2 > ✔️ Downloaded debian-12-nocloud-amd64.qcow2 > Installing Pre-Requisite libguestfs-tools onto Host E: Failed to fetch https://enterprise.proxmox.com/debian/ceph-squid/dists/trixie/InRelease 401 Unauthorized [IP: 66.70.154.82 443] > E: The repository 'https://enterprise.proxmox.com/debian/ceph-squid trixie InRelease' is not signed. > > [ERROR] in line 498: exit code 100: while executing command apt-get -qq update > /dev/null > > root@pve01:~# > ``` You have the enterprise repository enabled, this only works when you have a subscription. this is not related to the issue at hand: `nstalling Pre-Requisite libguestfs-tools onto Host E: Failed to fetch https://enterprise.proxmox.com/debian/ceph-squid/dists/trixie/InRelease 401 Unauthorized [IP: 66.70.154.82 443] > E: The repository 'https://enterprise.proxmox.com/debian/ceph-squid trixie InRelease' is not signed.`
saavagebueno commented 2025-11-20 05:17:22 -05:00
Author
Owner
Copy Link

@ekobres commented on GitHub (Oct 13, 2025):

Now I feel stupid. This was on a new host and I didn't even check to see if enterprise was enabled since it's always commented out in post-install! Now I have to retrace my steps and figure out how that snuck in.

@ekobres commented on GitHub (Oct 13, 2025): Now I feel stupid. This was on a new host and I didn't even check to see if enterprise was enabled since it's always commented out in post-install! Now I have to retrace my steps and figure out how that snuck in.
saavagebueno commented 2025-11-20 05:17:22 -05:00
Author
Owner
Copy Link

@Houtek commented on GitHub (Oct 14, 2025):

Hi,
stumbled across this issue.
I had this problem with virt-customize while trying to build some images (with terraform) too and had to install dhcpd-base on my Proxmox host (PVE 9.0.11)
I found the solution here: https://forum.proxmox.com/threads/virt-customize-install-broken.130473/post-797805

@Houtek commented on GitHub (Oct 14, 2025): Hi, stumbled across this issue. I had this problem with virt-customize while trying to build some images (with terraform) too and had to install dhcpd-base on my Proxmox host (PVE 9.0.11) I found the solution here: https://forum.proxmox.com/threads/virt-customize-install-broken.130473/post-797805
saavagebueno commented 2025-11-20 05:17:22 -05:00
Author
Owner
Copy Link

@jffluis commented on GitHub (Oct 14, 2025):

For now my solution was to duplicate a current Docker VM i had before and just delete the old containers/volumes to start fresh until this issue is properly fixed on PVE 9

@jffluis commented on GitHub (Oct 14, 2025): For now my solution was to duplicate a current Docker VM i had before and just delete the old containers/volumes to start fresh until this issue is properly fixed on PVE 9
saavagebueno commented 2025-11-20 05:17:23 -05:00
Author
Owner
Copy Link

@neight-allen commented on GitHub (Oct 14, 2025):

Houtek said:

I had this problem with virt-customize while trying to build some images (with terraform) too and had to install dhcpd-base on my Proxmox host (PVE 9.0.11)
I found the solution here: https://forum.proxmox.com/threads/virt-customize-install-broken.130473/post-797805

This workaround worked for me. TLDR: run apt install dhcpd-base on the host before running the install script.

MickLesk said:

yeah, its already in fixing, at ProxmoxVED. But its not so easy in PVE9 (virt-customize doesnt work fine). You can try the same Script with "ProxmoxVED" instead of "ProxmoxVE". (But you need to wait 5-10min after install for the post setup) - its not perfect at the moment, but im very busy this week :(

This workaround also worked for me. You do indeed have to let the VM "cook" for a bit after the install. TLDR: use this script for now bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/vm/docker-vm.sh)"

@neight-allen commented on GitHub (Oct 14, 2025): Houtek said: > I had this problem with virt-customize while trying to build some images (with terraform) too and had to install dhcpd-base on my Proxmox host (PVE 9.0.11) > I found the solution here: https://forum.proxmox.com/threads/virt-customize-install-broken.130473/post-797805 This workaround worked for me. TLDR: run `apt install dhcpd-base` on the host before running the install script. MickLesk said: > yeah, its already in fixing, at ProxmoxVED. But its not so easy in PVE9 (virt-customize doesnt work fine). You can try the same Script with "ProxmoxVED" instead of "ProxmoxVE". (But you need to wait 5-10min after install for the post setup) - its not perfect at the moment, but im very busy this week :( This workaround also worked for me. You do indeed have to let the VM "cook" for a bit after the install. TLDR: use this script for now `bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVED/main/vm/docker-vm.sh)"`
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#1783
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?