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

"✗ No Dashy Installation Found!" when trying to update LXC #267

New Issue
Closed
opened 2025-11-20 04:45:56 -05:00 by saavagebueno · 22 comments
saavagebueno commented 2025-11-20 04:45:56 -05:00
Owner
Copy Link

Originally created by @vdiogo on GitHub (Dec 30, 2024).

✅ Have you read and understood the above guidelines?

yes

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

dashy

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

bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/dashy.sh)"

📝 Provide a clear and concise description of the issue.

I installed Dashy via the helper scripts from TTEck and when I try to do an update, either by "update" or by pasting the command within the lxc shell an error message appears "No Dashy Installation Found" - even though dashy is installed and working well.

I have also tried creating a new container and starting from scratch (install Dashy and import the configuration) but get error also:
image

⚙️ What settings are you using?

  • Default Settings
  • Advanced Settings

🖥️ Which Linux distribution are you using?

Debian 12

🔄 Steps to reproduce the issue.

  1. Access the lxc console
  2. write update and press enter OR past the script command

❌ Paste the full error output (if available).

✗ No Dashy Installation Found!

🖼️ Additional context (optional).

image
Originally created by @vdiogo on GitHub (Dec 30, 2024). ### ✅ Have you read and understood the above guidelines? yes ### 📜 What is the name of the script you are using? dashy ### 📂 What was the exact command used to execute the script? bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/dashy.sh)" ### 📝 Provide a clear and concise description of the issue. I installed Dashy via the helper scripts from TTEck and when I try to do an update, either by "update" or by pasting the command within the lxc shell an error message appears "No Dashy Installation Found" - even though dashy is installed and working well. I have also tried creating a new container and starting from scratch (install Dashy and import the configuration) but get error also: <img width="1121" alt="image" src="https://github.com/user-attachments/assets/db153a2e-b89e-41a4-b83a-8f2723952c11" /> ### ⚙️ What settings are you using? - [X] Default Settings - [ ] Advanced Settings ### 🖥️ Which Linux distribution are you using? Debian 12 ### 🔄 Steps to reproduce the issue. 1. Access the lxc console 2. write update and press enter OR past the script command ### ❌ Paste the full error output (if available). ✗ No Dashy Installation Found! ### 🖼️ Additional context (optional). <img width="976" alt="image" src="https://github.com/user-attachments/assets/6ffdcef4-5027-426b-8196-17725d588658" />
saavagebueno commented 2025-11-20 04:45:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

  1. issue: Check if this exists: cd /opt/dashy and then do an ls -a, whats the output?
  2. issue: you dont have installed curl or have an massive dns issue on your proxmox, therefore you cant execute the bash script. The outputs are not normal and thats not a script issue
@MickLesk commented on GitHub (Dec 31, 2024): 1. issue: Check if this exists: cd /opt/dashy and then do an ls -a, whats the output? 2. issue: you dont have installed curl or have an massive dns issue on your proxmox, therefore you cant execute the bash script. The outputs are not normal and thats not a script issue
saavagebueno commented 2025-11-20 04:45:57 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Dec 31, 2024):

  1. issue: Check if this exists: cd /opt/dashy and then do an ls -a, whats the output?
  2. issue: you dont have installed curl or have an massive dns issue on your proxmox, therefore you cant execute the bash script. The outputs are not normal and thats not a script issue

Thanks for the prompt reply.

  1. See print screen -bash: cd: /opt/dashy: No such file or directory:
    image

  2. Apologies, how can I check if I have curl installed and/ or troubleshoot DNS issues in my proxmox?

@vdiogo commented on GitHub (Dec 31, 2024): > 1. issue: Check if this exists: cd /opt/dashy and then do an ls -a, whats the output? > 2. issue: you dont have installed curl or have an massive dns issue on your proxmox, therefore you cant execute the bash script. The outputs are not normal and thats not a script issue Thanks for the prompt reply. 1. See print screen `-bash: cd: /opt/dashy: No such file or directory`: <img width="639" alt="image" src="https://github.com/user-attachments/assets/6ca7aded-e3f7-46d0-829b-deba4aed20ae" /> 2. Apologies, how can I check if I have curl installed and/ or troubleshoot DNS issues in my proxmox?
saavagebueno commented 2025-11-20 04:45:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

  1. are you sure, thats an tteck script? dashy would be installed in /opt/ - looks not like an helper script?

  2. apt-get install curl on proxmox node

@MickLesk commented on GitHub (Dec 31, 2024): 1. are you sure, thats an tteck script? dashy would be installed in /opt/ - looks not like an helper script? 2. apt-get install curl on proxmox node
saavagebueno commented 2025-11-20 04:45:57 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

ive looked the history, in 2023 and early 2024 it was in /dashy, tteck changed it into /opt/dashy

save your configuration of dashy, copy or move the folder to /opt, or create an new lxc

@MickLesk commented on GitHub (Dec 31, 2024): ive looked the history, in 2023 and early 2024 it was in /dashy, tteck changed it into /opt/dashy save your configuration of dashy, copy or move the folder to /opt, or create an new lxc
saavagebueno commented 2025-11-20 04:45:58 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Dec 31, 2024):

1. are you sure, thats an tteck script? dashy would be installed in /opt/ - looks not like an helper script?
Yes, quite positive as all my lxc were installed using tteck scripts

2. apt-get install curl on proxmox node
Done and indeed curl was not installed.
Get same result upon trying to run the script on the newly created lxc (102) or running the same script in the existing contaoiner (109)
image

image
@vdiogo commented on GitHub (Dec 31, 2024): `1. are you sure, thats an tteck script? dashy would be installed in /opt/ - looks not like an helper script?` Yes, quite positive as all my lxc were installed using tteck scripts `2. apt-get install curl on proxmox node` Done and indeed curl was not installed. Get same result upon trying to run the script on the newly created lxc (102) or running the same script in the existing contaoiner (109) <img width="1176" alt="image" src="https://github.com/user-attachments/assets/d37951cc-f9be-4f1f-98dc-21418e2f4d55" /> <img width="1176" alt="image" src="https://github.com/user-attachments/assets/a21e9475-0c12-483f-a8e8-fc7e3dcb1958" />
saavagebueno commented 2025-11-20 04:45:58 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Dec 31, 2024):

As a matter of adding more info, I performed the following steps when trying to update:

  1. Accessed the existing container console
  2. Entered the command bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/dashy.sh)" add update
  3. Get displayed with this window and click Yes:
    image
  4. Get to this screen:
    image
@vdiogo commented on GitHub (Dec 31, 2024): As a matter of adding more info, I performed the following steps when trying to update: 1. Accessed the existing container console 2. Entered the command `bash -c "$(wget -qLO - https://github.com/community-scripts/ProxmoxVE/raw/main/ct/dashy.sh)"` add `update` 3. Get displayed with this window and click Yes: <img width="1176" alt="image" src="https://github.com/user-attachments/assets/77c000e7-788c-4df6-bbe0-d69bc95afc4b" /> 4. Get to this screen: <img width="1176" alt="image" src="https://github.com/user-attachments/assets/a8ee7aad-1fe9-4573-8fec-8cf64ac41052" />
saavagebueno commented 2025-11-20 04:45:58 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Dec 31, 2024):

ive looked the history, in 2023 and early 2024 it was in /dashy, tteck changed it into /opt/dashy

save your configuration of dashy, copy or move the folder to /opt, or create an new lxc

Thanks for looking into that. I'm trying to install it on a new lxc (102) but get an error (see above)

@vdiogo commented on GitHub (Dec 31, 2024): > ive looked the history, in 2023 and early 2024 it was in /dashy, tteck changed it into /opt/dashy > > save your configuration of dashy, copy or move the folder to /opt, or create an new lxc Thanks for looking into that. I'm trying to install it on a new lxc (102) but get an error (see above)
saavagebueno commented 2025-11-20 04:45:58 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

not in the container, run this in proxmox shell (curl, wget ...)
=> apt-get install

after this bash -c

@MickLesk commented on GitHub (Dec 31, 2024): not in the container, run this in proxmox shell (curl, wget ...) => apt-get install after this bash -c
saavagebueno commented 2025-11-20 04:45:58 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Dec 31, 2024):

not in the container, run this in proxmox shell (curl, wget ...) => apt-get install

after this bash -c

Sorry, yes that's what I did:

  1. Run apt-get install in the pve shell
  2. Run bash -c... in the container
@vdiogo commented on GitHub (Dec 31, 2024): > not in the container, run this in proxmox shell (curl, wget ...) => apt-get install > > after this bash -c Sorry, yes that's what I did: 1. Run apt-get install in the pve shell 2. Run bash -c... in the container
saavagebueno commented 2025-11-20 04:45:59 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Dec 31, 2024):

image
image
@vdiogo commented on GitHub (Dec 31, 2024): 1. <img width="1176" alt="image" src="https://github.com/user-attachments/assets/ed2e5b38-938d-4b7f-98d3-6f18bbb26f3a" /> 2. <img width="1176" alt="image" src="https://github.com/user-attachments/assets/f02b719c-6c4a-4d22-98cb-6c43c9c09914" />
saavagebueno commented 2025-11-20 04:45:59 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

Can you reboot? Something is broken on your Proxmox

@MickLesk commented on GitHub (Dec 31, 2024): Can you reboot? Something is broken on your Proxmox
saavagebueno commented 2025-11-20 04:45:59 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Dec 31, 2024):

Can you reboot? Something is broken on your Proxmox

Done (rebooted proxmox)... same result :/

@vdiogo commented on GitHub (Dec 31, 2024): > Can you reboot? Something is broken on your Proxmox Done (rebooted proxmox)... same result :/
saavagebueno commented 2025-11-20 04:45:59 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

Other Scripts works? Like Debian LXC or something?

@MickLesk commented on GitHub (Dec 31, 2024): Other Scripts works? Like Debian LXC or something?
saavagebueno commented 2025-11-20 04:45:59 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Dec 31, 2024):

Debian didn't worked on my new lxc (102) so I decided creating a new lxc with a different template and run the Debian script... and seems to have worked, until a point where a prompt asked if I wanted to update a security patch to which I answered yes, and been waiting for ~2h for it to finish

Previously I have chosen the standard Debian and now selected the second one (tgz format):
image

@vdiogo commented on GitHub (Dec 31, 2024): Debian didn't worked on my new lxc (102) so I decided creating a new lxc with a different template and run the Debian script... and seems to have worked, until a point where a prompt asked if I wanted to update a security patch to which I answered yes, and been waiting for ~2h for it to finish Previously I have chosen the standard Debian and now selected the second one (tgz format): <img width="747" alt="image" src="https://github.com/user-attachments/assets/f396cdb6-2e45-4c2f-af33-c71db8a81f01" />
saavagebueno commented 2025-11-20 04:45:59 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Dec 31, 2024):

Now I have created a new container (110) skipping that security update installation, and tried the Dashy script, and get this error:

image
@vdiogo commented on GitHub (Dec 31, 2024): Now I have created a new container (110) skipping that security update installation, and tried the Dashy script, and get this error: <img width="1591" alt="image" src="https://github.com/user-attachments/assets/6c881589-ec5d-4cd3-8229-64aaff52faef" />
saavagebueno commented 2025-11-20 04:45:59 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Dec 31, 2024):

You have massive Problems on your Proxmox.

Fix your Proxmox First. I cant Help, its not an Script issue

You cant call LXC's, Update and so on. Looks Like massive DNS Breaks

@MickLesk commented on GitHub (Dec 31, 2024): You have massive Problems on your Proxmox. Fix your Proxmox First. I cant Help, its not an Script issue You cant call LXC's, Update and so on. Looks Like massive DNS Breaks
saavagebueno commented 2025-11-20 04:46:00 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Jan 1, 2025):

You have massive Problems on your Proxmox.

Fix your Proxmox First. I cant Help, its not an Script issue

You cant call LXC's, Update and so on. Looks Like massive DNS Breaks

Why do you state so firmly that I have DNS issues? What logs gave you that hint?

@vdiogo commented on GitHub (Jan 1, 2025): > You have massive Problems on your Proxmox. > > Fix your Proxmox First. I cant Help, its not an Script issue > > You cant call LXC's, Update and so on. Looks Like massive DNS Breaks Why do you state so firmly that I have DNS issues? What logs gave you that hint?
saavagebueno commented 2025-11-20 04:46:00 -05:00
Author
Owner
Copy Link

@MickLesk commented on GitHub (Jan 1, 2025):

Your call cant call our GitHub build.func

@MickLesk commented on GitHub (Jan 1, 2025): Your call cant call our GitHub build.func
saavagebueno commented 2025-11-20 04:46:00 -05:00
Author
Owner
Copy Link

@MekongHigh commented on GitHub (Jan 2, 2025):

Previously I have chosen the standard Debian and now selected the second one (tgz format): image

Have you run the install script in the Proxmox VE Shell, or did you first created a lxc and then run install the script in the LXC shell?

@MekongHigh commented on GitHub (Jan 2, 2025): > > Previously I have chosen the standard Debian and now selected the second one (tgz format): <img alt="image" width="747" src="https://private-user-images.githubusercontent.com/24878195/399506557-f396cdb6-2e45-4c2f-af33-c71db8a81f01.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzU4MzY2MjUsIm5iZiI6MTczNTgzNjMyNSwicGF0aCI6Ii8yNDg3ODE5NS8zOTk1MDY1NTctZjM5NmNkYjYtMmU0NS00YzJmLWFmMzMtYzcxZGI4YTgxZjAxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAxMDIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMTAyVDE2NDUyNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE3YjIzNzI5ZWZjYTcyN2EyYTVjYWEyY2FmM2I1NWQyYTM2YjhmYjEwY2FjMWFiY2E1MmUwMjE1MWM3N2YwNjcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ff409C_uCxT5CvnF9oEUbBZwOw9q98zR4mhfOOOtCrY"> Have you run the install script in the Proxmox VE Shell, or did you first created a lxc and then run install the script in the LXC shell?
saavagebueno commented 2025-11-20 04:46:00 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Jan 2, 2025):

Previously I have chosen the standard Debian and now selected the second one (tgz format): image

Have you run the install script in the Proxmox VE Shell, or did you first created a lxc and then run install the script in the LXC shell?

I first created the lxc and then ran the script in the lxc shell

@vdiogo commented on GitHub (Jan 2, 2025): > > Previously I have chosen the standard Debian and now selected the second one (tgz format): <img alt="image" width="747" src="https://private-user-images.githubusercontent.com/24878195/399506557-f396cdb6-2e45-4c2f-af33-c71db8a81f01.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MzU4MzY2MjUsIm5iZiI6MTczNTgzNjMyNSwicGF0aCI6Ii8yNDg3ODE5NS8zOTk1MDY1NTctZjM5NmNkYjYtMmU0NS00YzJmLWFmMzMtYzcxZGI4YTgxZjAxLnBuZz9YLUFtei1BbGdvcml0aG09QVdTNC1ITUFDLVNIQTI1NiZYLUFtei1DcmVkZW50aWFsPUFLSUFWQ09EWUxTQTUzUFFLNFpBJTJGMjAyNTAxMDIlMkZ1cy1lYXN0LTElMkZzMyUyRmF3czRfcmVxdWVzdCZYLUFtei1EYXRlPTIwMjUwMTAyVDE2NDUyNVomWC1BbXotRXhwaXJlcz0zMDAmWC1BbXotU2lnbmF0dXJlPTE3YjIzNzI5ZWZjYTcyN2EyYTVjYWEyY2FmM2I1NWQyYTM2YjhmYjEwY2FjMWFiY2E1MmUwMjE1MWM3N2YwNjcmWC1BbXotU2lnbmVkSGVhZGVycz1ob3N0In0.ff409C_uCxT5CvnF9oEUbBZwOw9q98zR4mhfOOOtCrY"> > > Have you run the install script in the Proxmox VE Shell, or did you first created a lxc and then run install the script in the LXC shell? I first created the lxc and then ran the script in the lxc shell
saavagebueno commented 2025-11-20 04:46:00 -05:00
Author
Owner
Copy Link

@MekongHigh commented on GitHub (Jan 2, 2025):

I first created the lxc and then ran the script in the lxc shell

That is not the way these scripts work. These script also create the container.
To create a new Proxmox VE Dashy LXC, run the command below in the Proxmox VE Shell.

@MekongHigh commented on GitHub (Jan 2, 2025): > I first created the lxc and then ran the script in the lxc shell That is not the way these scripts work. These script also create the container. To create a new Proxmox VE Dashy LXC, run the command below in the Proxmox VE Shell.
saavagebueno commented 2025-11-20 04:46:00 -05:00
Author
Owner
Copy Link

@vdiogo commented on GitHub (Jan 2, 2025):

Ah, now we're talking :) Thanks

image
@vdiogo commented on GitHub (Jan 2, 2025): Ah, now we're talking :) Thanks <img width="709" alt="image" src="https://github.com/user-attachments/assets/e0e1bd0c-5e89-416c-af29-71dd28a10ef9" />
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
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#267
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?