2 Replies
I have found one more issue,
If i deploy any app using docker compose,
And run it till 2000+ log lines (as per my app code), then stop the container, and redeploy again after changing some codo line,
I can still see old logs,but if you are using any other builder like Heroku, nixpack etc and do as i said above,
No old log will be available because after stopping the container, Dokploy deletes the container, so we can see old logs.
@Aron
I agree, retaining logs would be better but right now it seems like Dokploy directly accesses Docker containers for their logs.
So there is no external Docker container log storage.
The option to persist the logs (automatically) even if the container gets deleted would require a new feature.