-
-
Notifications
You must be signed in to change notification settings - Fork 169
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
[Bug Report] Unable to Change Container Commands After Application is First Created #644
Comments
Same, it's bugging out |
Sorry its taken a little longer to get to your ticket, but the newest work is being done over at https://github.com/SelfhostedPro/yacht-nuxt which is more like a Yacht2.0. The latest image is yacht:devel please try that image and let us know if the problem has been resolved, what was done if it was resolved, or if you still need assistance. Please update or close the ticket as resolved. |
@wickedyoda that project seems to not be updated recently, i tried the i also couldn't find the image : yacht:devel |
I will verify yacht:devel in a bit and make sure the image is still online, but it should be. But devel is the latest build with patches. Its just not pushed to main. |
It looks like we are having a problem with the repo, I am going to speak to @SelfhostedPro about it and will update. Because we are unable to pull Yacht:latest, yacht:devel, and yacht:nightly images from any source. |
Describe the bug
When creating an application container, you are able to add commands to be fired upon container start. However, if you complete setup for your container and then attempt to change or add commands, you are never presented with the dialog to enter them.
To Reproduce
Steps to reproduce the behavior:
Expected behavior
You should be able to add or change commands regardless of the container being 'fresh' or 'active'
Screenshots
When creating the container from scratch:
After creating the container and clicking "edit" the "+" button does not work.
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: