Move docker resource limit settings from server to agent

[6543]

so you can set it per agent and not per server

related to #3156 to cleanup the step definition

[lafriks]

Maybe server can still provide defaults?

[codecov]

Codecov Report

Attention: Patch coverage is 0% with 42 lines in your changes missing coverage. Please review.

Project coverage is 26.54%. Comparing base (fcc57df) to head (68288ae).
Report is 2 commits behind head on main.

Files with missing lines	Patch %	Lines
pipeline/backend/docker/config.go	0.00%	27 Missing ⚠️
pipeline/backend/docker/docker.go	0.00%	8 Missing ⚠️
pipeline/backend/docker/convert.go	0.00%	7 Missing ⚠️

Additional details and impacted files

@@            Coverage Diff             @@
##             main    #3174      +/-   ##
==========================================
- Coverage   26.60%   26.54%   -0.07%     
==========================================
  Files         373      374       +1     
  Lines       27081    27045      -36     
==========================================
- Hits         7205     7178      -27     
+ Misses      19213    19210       -3     
+ Partials      663      657       -6     

Flag	Coverage Δ
	26.54% <0.00%> (-0.07%)	⬇️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[6543]

no I'm against this ...

we for example also do not set the tmp path for the local backend on the server side

[lafriks]

I have no strong opinion about this but that would avoid it being breaking change

[6543]

well so it looks like v3.0.0 is right around the corner

[anbraten]

I think it the default fits well into the agent settings, specific settings however should probably be still settable via the pipeline config. We just need to move it into the backend config section.

[6543]

well make it non breaking for now then ... but add a TODO comment so we can do so on next majour bump

also I add a docker specific config like with kubernetis for limiting per step

[woodpecker-bot]

Tearing down https://woodpecker-ci-woodpecker-pr-3174.surge.sh

[pat-s]

Fits better into the agent than server but I agree, it should be settable in the step config like for k8s, as every container usually has a different requirement.

Given it's breaking due to the move, it fits well into 3.0.

[6543]

yes have it alser per stes should be an backend option like done for kubes settings. this will be a new issue to address ...