Closed sashathomas closed 4 months ago
Hi @sashathomas,
Thank you for reporting this and sorry you had troubles.
IP octet
field empty and Reboot
field at Nop
value (see screenshot) Once the Instance is created you can see the restart and destroy operations on the listing and by going to the instance view, you will see some extra operations for this instance
I hope this helps. Let me know how it goes and i'll try to fix the bug you mentioned shortly.
@proditis Adding the server was the solution. Thank you! I configured a new server in the mUI and I can spawn/destroy/reboot private instances from the pUI now. Thanks for looking into that other bug as well!
Great i'm glad this was it and it worked out.
Closing this issue. Feel free to open a new one for any other problems you may have.
Describe the bug Having a couple issues with private instances of targets. First, creating a new private target from the mUI results in a 500 error. Afterwards, both the mUI and the pUI think the private instance have been created, but the docker container is never started. Second, and this could be my fault, but there is no option from the pUI to spawn/reboot/destroy private instances, even for targets which are marked as spinnable and private instances being checked. Not sure if there is something I'm missing there.
To Reproduce Steps to reproduce the behavior:
docker ps -a
and observe that no container was created for the private instance.I apologize if this isn't enough information, this is basically the out-of-the-box configuration for the all-in-one solution. Please let me know if there is anything else I can provide, thanks!