Closed aikawame closed 3 weeks ago
@aikawame Thank you for the reporting!
This panic seems to be caused by the failure to find the container specified by --watch-container application
.
https://github.com/kayac/ecspresso/blob/99d873bab684e08ef3de33dda37d9f676b16e9b7/run.go#L79-L80
If the watchContainer
is nil, raise a panic at *watchContainer.Name
.
Please check for your task definition. Does it have a container definition named application
?
By the way, this panic is undesirable. I'll fix it to return an error if a container definition is not found.
@fujiwara Thank you for your quick reply!
As you said, this problem was caused by the wrong container name. And thank you for your help in fixing panic.
I encountered the error
panic: runtime error: invalid memory address or nil pointer dereference
, so I report this.Command:
The detailed error message is below.
Dry-run worked fine, but when I run the actual command, it looks like the above.