remove undocumented docker specific option

[6543]

No description provided.

[codecov-commenter]

Codecov Report

Patch coverage has no change and project coverage change: -0.05 ⚠️

Comparison is base (ea895ba) 39.03% compared to head (d0c7062) 38.99%.

❗ Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #1825      +/-   ##
==========================================
- Coverage   39.03%   38.99%   -0.05%     
==========================================
  Files         168      168              
  Lines       10502    10500       -2     
==========================================
- Hits         4099     4094       -5     
- Misses       6138     6141       +3     
  Partials      265      265              

Impacted Files	Coverage Δ
pipeline/backend/docker/convert.go	8.66% <ø> (+0.06%)	⬆️
pipeline/frontend/yaml/compiler/convert.go	0.00% <ø> (ø)
pipeline/frontend/yaml/container.go	77.77% <ø> (ø)

... and 1 file with indirect coverage changes

☔ View full report in Codecov by Sentry.
📢 Do you have feedback about the report comment? Let us know in this issue.

[gapodo]

Hi,

short note from my side, removin this will likely result in it being requested for readdition soon(tm), as esp. with K8s there is often a need to label containers for them to be able to run (depends on the k8s setup, but things like network restrictions,... are often applied via labels (or annotations)).

Though this could/should potentially be a seperate issue / rfc / FR as to how we handle backend specific options?

[6543]

well in that case it will be a k8s specific backend option yes

[6543]

@gapodo https://woodpecker-ci.org/docs/next/administration/backends/kubernetes#resources

[gapodo]

@gapodo https://woodpecker-ci.org/docs/next/administration/backends/kubernetes#resources

Oh, thx, sorry had some troubles keeping up with all the changes... Since it's cared for by the new backend_options (where it should be implemented in that case), you can disregard my note.