Closed mupsje closed 2 months ago
Are you using SSH?
🏁 The script runs without any problems from this end.
____ __
/ __ \____ _____/ /______ ____
/ / / / __ \/ ___/ //_/ __ `/ _ \
/ /_/ / /_/ / /__/ ,< / /_/ / __/
/_____/\____/\___/_/|_|\__, /\___/
/____/
Using Advanced Settings
Using Distribution: debian
Using debian Version: 12
Using Container Type: 1
Using Root Password: Automatic Login
Container ID: 111
Using Hostname: dockge
Using Disk Size: 18
Allocated Cores: 2
Allocated RAM: 2048
Using Bridge: vmbr0
Using IP Address: dhcp
Using Gateway IP Address: Default
Using APT-Cacher IP Address: Default
Disable IPv6: yes
Using Interface MTU Size: Default
Using DNS Search Domain: Host
Using DNS Server IP Address: Host
Using MAC Address: AE:1A:60:07:B7:59
Using Vlan: Default
Enable Root SSH Access: no
Enable Verbose Mode: no
Creating a Dockge LXC using the above advanced settings
✓ Using local for Template Storage.
✓ Using thin-pool for Container Storage.
✓ Updated LXC Template List
✓ LXC Container 111 was successfully created.
✓ Started LXC Container
✓ Set up Container OS
✓ Network Connected: 192.168.86.250
✓ IPv4 Internet Connected
✗ IPv6 Internet Not Connected
✓ DNS Resolved github.com to 140.82.112.3
✓ Updated Container OS
✓ Installed Dependencies
✓ Installed Docker v27.2.1
✓ Installed Docker Compose v2.29.4
✓ Installed Dockge
Would you like to add Immich? <y/N>
Would you like to add Home Assistant? <y/N>
✓ Customized Container
✓ Cleaned
✓ Completed Successfully!
Dockge should be reachable by going to the following URL.
http://192.168.86.250:5001
🧐 As this issue is unrelated to the script, it is considered closed.
Are you using SSH?
no shell in proxmox
Please verify that you have read and understood the guidelines.
yes
A clear and concise description of the issue.
bash: warning: setlocale: LC_ALL: cannot change locale (en_US.UTF8)
What settings are you currently utilizing?
Default Settings
Which Linux distribution are you employing?
Debian 12
If relevant, including screenshots or a code block can be helpful in clarifying the issue.
Please provide detailed steps to reproduce the issue.
No response