[GH-ISSUE #9955] Docker LXC script is not utilizing App Defaults #2162

Closed
opened 2026-02-26 12:51:31 +03:00 by kerem · 1 comment
Owner

Originally created by @Furglitch on GitHub (Dec 14, 2025).
Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9955

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?

Docker (LXC)

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

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

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

📈 Which Proxmox version are you on?

pve-manager/9.0.4/39d8a4de7dfb2c40 (running kernel: 6.8.12-8-pve)

📝 Provide a clear and concise description of the issue.

When running the Docker LXC helper script and selecting 'App Defaults for Docker', it appears to be using the script's defaults, rather than defaults created by the user from previous runs.

The final CT shows that that it was indeed created with incorrect settings such as 2GB RAM instead of 4GB, 4GB disk size over 32GB,
Image
as well as using DHCP instead of the given static IP information
Image

🔄 Steps to reproduce the issue.

  1. Set docker.vars to use user-created defaults over script-created defaults (personal is provided in 'Additional Context')
  2. Run the docker LXC helper script
  3. Select 'App Defaults for Docker'
  4. Note the differences between the defaults file and script output
  5. Verify incorrect settings in the final container

Paste the full error output (if available).

Note: this is the output with verbose enabled in the docker.vars file

    ____             __            
   / __ \____  _____/ /_____  _____
  / / / / __ \/ ___/ //_/ _ \/ ___/
 / /_/ / /_/ / /__/ ,< /  __/ /    
/_____/\____/\___/_/|_|\___/_/     
                                   
  ⚙️  Using App Defaults for Docker on node pve
  ✔️   Loaded /usr/local/community-scripts/defaults/docker.vars
  💡  PVE Version 9.0.4 (Kernel: 6.8.12-8-pve)
  🆔  Container ID: 101
  🖥️  Operating System: debian (12)
  📦  Container Type: Unprivileged
  💾  Disk Size: 4 GB
  🧠  CPU Cores: 2
  🛠️  RAM Size: 2048 MiB
  🎮  GPU Passthrough: Enabled
  🚀  Creating a Docker LXC using the above default settings
  
  ✔️   Storage local (Free: 74.1MB  Used: 15.1MB) [Template]
  ✔️   Storage local-lvm (Free: 298.1MB  Used: 49.9MB) [Container]
  ✔️   Storage 'local-lvm' (lvmthin) validated
  ✔️   Template storage 'local' validated
  ✔️   Template search completed
  ✔️   Template debian-12-standard_12.12-1_amd64.tar.zst [online]
  ✔️   LXC Container 101 was successfully created.
 🎮 Detected AMD GPU
  ✔️   Automatically configuring AMD GPU passthrough
  ✔️   AMD GPU passthrough configured (2 devices)
  ✔️   Started LXC Container
  ✔️   Network in LXC is reachable (ping)
  ✔️   GPU passthrough configured (video:44, render:104)
  ✔️   Customized LXC Container
  ✔️   Set up Container OS
  ✔️   Network Connected: 192.168.1.34 2600:8803:8002:cb00:be24:11ff:fe27:def8 
  ✔️   IPv4 Internet Connected
  ✔️   IPv6 Internet Connected
  ✔️   Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ )
  ✔️   Updated Container OS
  ✔️   Installed Docker docker-v29.1.3
      Install Docker Compose v2 plugin? <y/N> y
  ✔️   Installed Docker Compose v5.0.0
      Would you like to add Portainer (UI)? <y/N> n
      Would you like to install the Portainer Agent (for remote management)? <y/N> n
      Expose Docker TCP socket (insecure) ? [n = No, l = Local only (127.0.0.1), a = All interfaces (0.0.0.0)] <n/l/a>: a
  ✔️   Docker TCP socket available on tcp://0.0.0.0:2375
  ✔️   Customized Container
  ✔️   Cleaned
  ✔️   Completed Successfully!

  🚀  Docker setup has been successfully initialized!
  💡   If you installed Portainer, access it at the following URL:
    🌐  https://192.168.1.34:9443
root@pve:~# 

🖼️ Additional context (optional).

/usr/local/community-scripts/defaults/docker.vars

root@pve:~# cat /usr/local/community-scripts/defaults/docker.vars
# App-specific defaults for Docker (docker)
# Generated on 2025-12-14T19:05:14Z

var_unprivileged=1
var_cpu=2
var_ram=4096
var_disk=32
var_brg=vmbr0
var_net=192.168.1.210/24
var_gateway=192.168.1.1
var_ipv6_method=auto
var_ssh=yes
var_apt_cacher=no
var_fuse=no
var_tun=yes
var_gpu=yes
var_nesting=1
var_keyctl=1
var_mknod=1
var_mount_fs=nfs, ext4
var_protection=yes
var_timezone=America/Chicago
var_tags=
var_verbose=yes
var_hostname=docker
var_template_storage=local
var_container_storage=local-lvm
Originally created by @Furglitch on GitHub (Dec 14, 2025). Original GitHub issue: https://github.com/community-scripts/ProxmoxVE/issues/9955 ### ✅ 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? Docker (LXC) ### 📂 What was the exact command used to execute the script? bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/docker.sh)" ### ⚙️ What settings are you using? - [ ] Default Settings - [x] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 📈 Which Proxmox version are you on? pve-manager/9.0.4/39d8a4de7dfb2c40 (running kernel: 6.8.12-8-pve) ### 📝 Provide a clear and concise description of the issue. When running the Docker LXC helper script and selecting 'App Defaults for Docker', it appears to be using the script's defaults, rather than defaults created by the user from previous runs. The final CT shows that that it was indeed created with incorrect settings such as 2GB RAM instead of 4GB, 4GB disk size over 32GB, <img width="589" height="388" alt="Image" src="https://github.com/user-attachments/assets/fedc14b5-134d-4c87-8583-6150729401fb" /> as well as using DHCP instead of the given static IP information <img width="1094" height="398" alt="Image" src="https://github.com/user-attachments/assets/82207a98-fd33-44eb-9ca8-491fdeb0873b" /> ### 🔄 Steps to reproduce the issue. 1. Set docker.vars to use user-created defaults over script-created defaults (personal is provided in 'Additional Context') 2. Run the docker LXC helper script 3. Select 'App Defaults for Docker' 4. Note the differences between the defaults file and script output 5. Verify incorrect settings in the final container ### ❌ Paste the full error output (if available). *Note: this is the output with verbose enabled in the docker.vars file* ``` ____ __ / __ \____ _____/ /_____ _____ / / / / __ \/ ___/ //_/ _ \/ ___/ / /_/ / /_/ / /__/ ,< / __/ / /_____/\____/\___/_/|_|\___/_/ ⚙️ Using App Defaults for Docker on node pve ✔️ Loaded /usr/local/community-scripts/defaults/docker.vars 💡 PVE Version 9.0.4 (Kernel: 6.8.12-8-pve) 🆔 Container ID: 101 🖥️ Operating System: debian (12) 📦 Container Type: Unprivileged 💾 Disk Size: 4 GB 🧠 CPU Cores: 2 🛠️ RAM Size: 2048 MiB 🎮 GPU Passthrough: Enabled 🚀 Creating a Docker LXC using the above default settings ✔️ Storage local (Free: 74.1MB Used: 15.1MB) [Template] ✔️ Storage local-lvm (Free: 298.1MB Used: 49.9MB) [Container] ✔️ Storage 'local-lvm' (lvmthin) validated ✔️ Template storage 'local' validated ✔️ Template search completed ✔️ Template debian-12-standard_12.12-1_amd64.tar.zst [online] ✔️ LXC Container 101 was successfully created. 🎮 Detected AMD GPU ✔️ Automatically configuring AMD GPU passthrough ✔️ AMD GPU passthrough configured (2 devices) ✔️ Started LXC Container ✔️ Network in LXC is reachable (ping) ✔️ GPU passthrough configured (video:44, render:104) ✔️ Customized LXC Container ✔️ Set up Container OS ✔️ Network Connected: 192.168.1.34 2600:8803:8002:cb00:be24:11ff:fe27:def8 ✔️ IPv4 Internet Connected ✔️ IPv6 Internet Connected ✔️ Git DNS: github.com:(✔️ ) raw.githubusercontent.com:(✔️ ) api.github.com:(✔️ ) git.community-scripts.org:(✔️ ) ✔️ Updated Container OS ✔️ Installed Docker docker-v29.1.3 Install Docker Compose v2 plugin? <y/N> y ✔️ Installed Docker Compose v5.0.0 Would you like to add Portainer (UI)? <y/N> n Would you like to install the Portainer Agent (for remote management)? <y/N> n Expose Docker TCP socket (insecure) ? [n = No, l = Local only (127.0.0.1), a = All interfaces (0.0.0.0)] <n/l/a>: a ✔️ Docker TCP socket available on tcp://0.0.0.0:2375 ✔️ Customized Container ✔️ Cleaned ✔️ Completed Successfully! 🚀 Docker setup has been successfully initialized! 💡 If you installed Portainer, access it at the following URL: 🌐 https://192.168.1.34:9443 root@pve:~# ``` ### 🖼️ Additional context (optional). /usr/local/community-scripts/defaults/docker.vars ```bash root@pve:~# cat /usr/local/community-scripts/defaults/docker.vars # App-specific defaults for Docker (docker) # Generated on 2025-12-14T19:05:14Z var_unprivileged=1 var_cpu=2 var_ram=4096 var_disk=32 var_brg=vmbr0 var_net=192.168.1.210/24 var_gateway=192.168.1.1 var_ipv6_method=auto var_ssh=yes var_apt_cacher=no var_fuse=no var_tun=yes var_gpu=yes var_nesting=1 var_keyctl=1 var_mknod=1 var_mount_fs=nfs, ext4 var_protection=yes var_timezone=America/Chicago var_tags= var_verbose=yes var_hostname=docker var_template_storage=local var_container_storage=local-lvm ```
kerem 2026-02-26 12:51:31 +03:00
  • closed this issue
  • added the
    bug
    label
Author
Owner

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

Duplicate of #9950

<!-- gh-comment-id:3652232164 --> @MickLesk commented on GitHub (Dec 14, 2025): Duplicate of #9950
Sign in to join this conversation.
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
starred/ProxmoxVE#2162
No description provided.