Closed samuel-p closed 2 years ago
@samuel-p just a workaround: could you kill the container and start with same version after xorm migration was done
does it work after the second/third restart?
I restarted the container several times without success and got the same logs every time. I now switched to the v0.14.3
tag and it seems to work again so far.
@samuel-p can you start with LogLevel = trace and send me the logs (from server & agent)
& what type of database do you use?
I updated the debug
-Logs in my first post with the trace
-Logs. I use Postgres as database. The agent seems to work so far with the latest version.
ok the issue is due the #474 rework ...
@samuel-p can you test the docker image woodpeckerci/woodpecker-server:codeberg-test
PS: please do not upgrade the agent as there is an issue with the backend-engine-detection (#542)
if this fix it #544 can go in :)
Yes it works! I got a lot of warnings from xorm
at the beginning, but after that it works (at least for me). Thank you.
xorm warnings are ok - they just point out that the colum types do not match exact to what xorm would propose if table would be recreated - there is no downside in functionality ...
and good to hear :) !
Component
server
Describe the bug
I tried updating my docker-compose setup to the latest version, but the server didn't came up. The only logs I got (using
--log-level=trace
) is this:System Info
Additional context
No response
Validations