Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Docker VM Script ERROR - Line 377 #1741

Closed
2 tasks done
hickmjr opened this issue Jan 25, 2025 · 4 comments
Closed
2 tasks done

Docker VM Script ERROR - Line 377 #1741

hickmjr opened this issue Jan 25, 2025 · 4 comments

Comments

@hickmjr
Copy link

hickmjr commented Jan 25, 2025

βœ… 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 "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/vm/docker-vm.sh)"

πŸ“ Provide a clear and concise description of the issue.

Upon running helper script for Docker VM, get ERROR on line 377; exit code 5, which terminates the script run.

βš™οΈ What settings are you using?

  • Default Settings
  • Advanced Settings

πŸ–₯️ Which Linux distribution are you using?

No response

πŸ”„ Steps to reproduce the issue.

❌ Paste the full error output (if available).

Using Default Settings
Using Virtual Machine ID: 103
Using Machine Type: i440fx
Using Disk Cache: None
Using Hostname: docker
Using CPU Model: KVM64
Allocated Cores: 2
Allocated RAM: 4096
Using Bridge: vmbr0
Using MAC Address: 02:83:2B:27:4D:1C
Using VLAN: Default
Using Interface MTU Size: Default
Start VM when completed: yes
Creating a Docker VM using the above default settings
βœ“ Using local-lvm for Storage Location.
βœ“ Virtual Machine ID is 103.
βœ“ https://cloud.debian.org/images/cloud/bookworm/latest/debian-12-nocloud-amd64.qcow2

[ERROR] in line 377: exit code 5: while executing command wget -q --show-progress $URL

πŸ–ΌοΈ Additional context (optional).

Image

@obiwantoby
Copy link

obiwantoby commented Jan 25, 2025

Well - this is occurring for the Debian script as well. Their Let's Encrypt Certificate was renewed today with the wrong mismatched domain.

At least for Debian.

Image

@hickmjr
Copy link
Author

hickmjr commented Jan 25, 2025

Image

Looks like an invalid certificate is the issue in this case.

@MickLesk
Copy link
Member

Can be closed?

@hickmjr
Copy link
Author

hickmjr commented Jan 26, 2025

issue resolved now that Debian fixed their cert.

@hickmjr hickmjr closed this as completed Jan 26, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants