Log view from stack, shows log from containers not in stack.
I will add more detail if I find anything. In terms of reproducibility, my first stack was setup from scratch. It points to a repo defined in the /repos page. The second stack I deployed, was a clone/copy, with a different compose specified.
Originally created by @harley-codes on GitHub (Jul 22, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/675
Log view from stack, shows log from containers not in stack.
I will add more detail if I find anything. In terms of reproducibility, my first stack was setup from scratch. It points to a repo defined in the /repos page. The second stack I deployed, was a clone/copy, with a different compose specified.
<img width="1640" height="718" alt="Image" src="https://github.com/user-attachments/assets/c92d9a7d-500a-4038-a15c-e1012ca0cd0b" />
It appears to get worse. I had a feeling it was due to cloning.. When I clicked destroy on one stack, it ended up taking out both. Fortunately it did not take out the stack config. So I was able to quickly redeploy before my session expired.
I can confirm, this error is as a result of using the copy function as found in the top left corner of the stack page.
<!-- gh-comment-id:3102634237 -->
@harley-codes commented on GitHub (Jul 22, 2025):
It appears to get worse. I had a feeling it was due to cloning.. When I clicked destroy on one stack, it ended up taking out both. Fortunately it did not take out the stack config. So I was able to quickly redeploy before my session expired.
I can confirm, this error is as a result of using the copy function as found in the top left corner of the stack page.
If two stack are on same server with same custom project name set, it is expected to lead to this behavior. If on same server the stacks need different project names.
<!-- gh-comment-id:3104680845 -->
@mbecker20 commented on GitHub (Jul 22, 2025):
If two stack are on same server with same custom project name set, it is expected to lead to this behavior. If on same server the stacks need different project names.
I may have missed that field when updating after copy. Ok if that is the expected behavior for projects the I assume this is it. Will close.
<!-- gh-comment-id:3106722861 -->
@harley-codes commented on GitHub (Jul 23, 2025):
I may have missed that field when updating after copy. Ok if that is the expected behavior for projects the I assume this is it. Will close.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @harley-codes on GitHub (Jul 22, 2025).
Original GitHub issue: https://github.com/moghtech/komodo/issues/675
Log view from stack, shows log from containers not in stack.
I will add more detail if I find anything. In terms of reproducibility, my first stack was setup from scratch. It points to a repo defined in the /repos page. The second stack I deployed, was a clone/copy, with a different compose specified.
@harley-codes commented on GitHub (Jul 22, 2025):
It appears to get worse. I had a feeling it was due to cloning.. When I clicked destroy on one stack, it ended up taking out both. Fortunately it did not take out the stack config. So I was able to quickly redeploy before my session expired.
I can confirm, this error is as a result of using the copy function as found in the top left corner of the stack page.
@mbecker20 commented on GitHub (Jul 22, 2025):
Are they supposed to be on different servers?
@mbecker20 commented on GitHub (Jul 22, 2025):
If two stack are on same server with same custom project name set, it is expected to lead to this behavior. If on same server the stacks need different project names.
@harley-codes commented on GitHub (Jul 23, 2025):
I may have missed that field when updating after copy. Ok if that is the expected behavior for projects the I assume this is it. Will close.