-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
Description
β Have you read and understood the above guidelines?
yes
π What is the name of the script you are using?
ct/nextcloudpi.sh
π What was the exact command used to execute the script?
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nextcloudpi.sh)"
βοΈ What settings are you using?
- Default Settings
- Advanced Settings
π₯οΈ Which Linux distribution are you using?
No response
π Provide a clear and concise description of the issue.
This is a folowup to #4817
I dont think this is related to DNS. Here is the output when I select "Advanced setting" from the menu.
bash -c "$(curl -fsSL https://raw.githubusercontent.com/community-scripts/ProxmoxVE/main/ct/nextcloudpi.sh)"
_ __ __ ________ ______ _
/ | / /__ _ / // / / __ / / __ ()
/ |/ / _ | |// __/ / / / __ / / / / __ / // / /
/ /| / __/> </ // // / // / // / // / __/ /
// |/_//||_/_//_/_,/_,// //
π§© Using Advanced Settings on node pve
π₯οΈ Operating System: debian
π Version: 12
π¦ Container Type: Unprivileged
π Root Password: ********
π Container ID: 101
π Hostname: nextcloudpi
πΎ Disk Size: 8 GB
π§ CPU Cores: 2
π οΈ RAM Size: 2048 MiB
π Bridge: vmbr0
π‘ IP Address: dhcp
π Gateway IP Address: Default
π‘ APT-Cacher IP Address: Default
π« Disable IPv6: no
βοΈ Interface MTU Size: Default
π DNS Search Domain: Host
π‘ DNS Server IP Address: Host
π·οΈ Vlan: Default
π‘ Tags: community-script;cloud
π Root SSH Access: no
ποΈ Enable FUSE Support: no
π Verbose Mode: no
π Creating a NextCloudPi LXC using the above advanced settings
βοΈ Using local for Template Storage.
βοΈ Using local-lvm for Container Storage.
βοΈ Updated LXC Template List
βοΈ LXC Template is ready to use.
βοΈ LXC Container 101 was successfully created.
βοΈ Started LXC Container
βοΈ Set up Container OS
βοΈ Network Connected: 2600:4040:2883:da00:be24:11ff:fe89:d8c
βοΈ IPv4 Internet Not Connected
βοΈ IPv6 Internet Connected
βοΈ DNS Lookup Failure
βοΈ Updated Container OS
β Έ/dev/stdin: line 72: curl: command not found
[ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1
/dev/stdin: line 84: post_update_to_api: command not found
/dev/stdin: line 218: pop_var_context: head of shell_variables not a function context
/dev/stdin: line 14: pop_var_context: head of shell_variables not a function context
/dev/fd/63: line 74: SPINNER_PID: unbound variable
root@pve:~#
And Here is the output when I select "Default Settings"
_ __ __ ________ ______ _
/ | / /__ _ / // / / __ / / __ ()
/ |/ / _ | |// __/ / / / __ / / / / __ / // / /
/ /| / __/> </ // // / // / // / // / __/ /
// |/_//||_/_//_/_,/_,// //
βοΈ Using Default Settings on node pve
π₯οΈ Operating System: debian
π Version: 12
π¦ Container Type: Unprivileged
πΎ Disk Size: 8 GB
π§ CPU Cores: 2
π οΈ RAM Size: 2048 MiB
π Container ID: 101
π Creating a NextCloudPi LXC using the above default settings
βοΈ Using local for Template Storage.
βοΈ Using local-lvm for Container Storage.
βοΈ Updated LXC Template List
βοΈ LXC Template is ready to use.
βοΈ LXC Container 101 was successfully created.
βοΈ Started LXC Container
βοΈ Set up Container OS
βοΈ Network Connected: 192.168.1.191 2600:4040:2883:da00:be24:11ff:fe12:88fc
βοΈ IPv4 Internet Connected
βοΈ IPv6 Internet Connected
βοΈ DNS Resolved github.com to 140.82.113.4
βοΈ Updated Container OS
βοΈ Core dependencies installed
βοΈ Installed NextCloudPi
βοΈ Customized Container
βοΈ Cleaned
βοΈ Completed Successfully!
π NextCloudPi setup has been successfully initialized!
π‘ Access it using the following URL:
π http://192.168.1.191/
root@pve:~#
This is installed on the same PVE server. Only difference is the Default vs advanced settings.
π Steps to reproduce the issue.
Tried the script with default settings (no user input) and it works as expected. And then tried it with "Advanced setting" and the script fails. The same server is used for both cases so there is no issue with DNS on the "Default settings"
β Paste the full error output (if available).
`/ | / /__ _ / // / / __ / / __ ()
/ |/ / _ | |// __/ / / / __ / / / / __ / // / /
/ /| / __/> </ // // / // / // / // / __/ /
// |///||////,/,// //
π§© Using Advanced Settings on node pve
π₯οΈ Operating System: debian
π Version: 12
π¦ Container Type: Unprivileged
π Root Password: ********
π Container ID: 101
π Hostname: nextcloudpi
πΎ Disk Size: 8 GB
π§ CPU Cores: 2
π οΈ RAM Size: 2048 MiB
π Bridge: vmbr0
π‘ IP Address: dhcp
π Gateway IP Address: Default
π‘ APT-Cacher IP Address: Default
π« Disable IPv6: no
βοΈ Interface MTU Size: Default
π DNS Search Domain: Host
π‘ DNS Server IP Address: Host
π·οΈ Vlan: Default
π‘ Tags: community-script;cloud
π Root SSH Access: no
ποΈ Enable FUSE Support: no
π Verbose Mode: no
π Creating a NextCloudPi LXC using the above advanced settings
βοΈ Using local for Template Storage.
βοΈ Using local-lvm for Container Storage.
βοΈ Updated LXC Template List
βοΈ LXC Template is ready to use.
βοΈ LXC Container 101 was successfully created.
βοΈ Started LXC Container
βοΈ Set up Container OS
βοΈ Network Connected: 2600:4040:2883:da00:be24:11ff:fe89:d8c
βοΈ IPv4 Internet Not Connected
βοΈ IPv6 Internet Connected
βοΈ DNS Lookup Failure
βοΈ Updated Container OS
β Έ/dev/stdin: line 72: curl: command not found
[ERROR] in line 51: exit code 0: while executing command "$@" > /dev/null 2>&1
/dev/stdin: line 84: post_update_to_api: command not found
/dev/stdin: line 218: pop_var_context: head of shell_variables not a function context
/dev/stdin: line 14: pop_var_context: head of shell_variables not a function context
/dev/fd/63: line 74: SPINNER_PID: unbound variable
root@pve:~#`
πΌοΈ Additional context (optional).
No response