Failing to deploy app; no errors in logs #421
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#421
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
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?
My images might be the problem:
This should be in logs?
Great logs @codegod100, thank you!
abra app errors
is supposed to help with this but I believe it still has bugs. I think the container never comes up, so this kind of helpful logging never comes into the logs. But it is available elsewhere in the JSON payload that the runtime returns. We definitely need to get these logs out because it's just a blackbox otherwise.Related: #339
Why have separate logs and errors commands? Intuitively I expect to find errors in the logs
Yeh, that's a good point! I guess I was just following the same model of the docker CLI, that it wasn't giving out these errors via the logs command and was to be found elsewhere. But yeh, we could pile this logic into the
logs
command? Just check if the container is flapping, if there are healthcheck errors, etc. before polling for logs? Smaller CLI surface is nicer. The logic needs to be improved, theerrors
command doesn't really work atm.Converging on #501.