Skip to content

pkg/pillar: remove unsupported linuxkit build.yml fields#5662

Merged
eriknordmark merged 1 commit intolf-edge:masterfrom
rucoder:rucoder/upgrade-linuxkit
Mar 9, 2026
Merged

pkg/pillar: remove unsupported linuxkit build.yml fields#5662
eriknordmark merged 1 commit intolf-edge:masterfrom
rucoder:rucoder/upgrade-linuxkit

Conversation

@rucoder
Copy link
Copy Markdown
Contributor

@rucoder rucoder commented Mar 7, 2026

Description

Remove security_opt and ports fields from pkg/pillar/build-dev.yml and pkg/pillar/build-k-dev.yml.

These fields are Docker Compose-specific and have never been valid in linuxkit package build.yml files. They were silently ignored by older linuxkit versions. The upcoming linuxkit upgrade introduces strict YAML validation that rejects unknown fields, causing the build to fail with:

Error: yaml: unmarshal errors:
  line 33: field security_opt not found in type moby.ImageConfig
  line 35: field ports not found in type moby.ImageConfig

This is a prerequisite cleanup before upgrading linuxkit to the latest version.

How to test and validate this PR

Run make eve-pillar and verify the build completes without YAML validation errors.

Changelog notes

No user-facing changes.

PR Backports

  • 16.0-stable: yes
  • 14.5-stable: yes ifzks is available
  • 13.4-stable: No

Checklist

  • I've provided a proper description

  • I've added the proper documentation

  • I've tested my PR on amd64 device

  • I've tested my PR on arm64 device

  • I've written the test verification instructions

  • I've set the proper labels to this PR

  • I've checked the boxes above, or I've provided a good reason why I didn't check them.

Remove security_opt and ports fields from build-dev.yml and
build-k-dev.yml. These are Docker Compose-specific fields that
have never been valid in linuxkit package build.yml files and
were silently ignored by older linuxkit versions.

The upcoming linuxkit upgrade introduces strict YAML validation
that rejects unknown fields, so these must be removed first.

Signed-off-by: Mikhail Malyshev <mike.malyshev@gmail.com>
@codecov
Copy link
Copy Markdown

codecov Bot commented Mar 7, 2026

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 29.49%. Comparing base (2281599) to head (3320150).
⚠️ Report is 349 commits behind head on master.

Additional details and impacted files
@@            Coverage Diff             @@
##           master    #5662      +/-   ##
==========================================
+ Coverage   19.52%   29.49%   +9.96%     
==========================================
  Files          19       18       -1     
  Lines        3021     2417     -604     
==========================================
+ Hits          590      713     +123     
+ Misses       2310     1552     -758     
- Partials      121      152      +31     

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

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Copy link
Copy Markdown
Contributor

@rene rene left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@rucoder
Copy link
Copy Markdown
Contributor Author

rucoder commented Mar 8, 2026

@rene do you know why CodeCov is 331 commit behind ?

@eriknordmark eriknordmark merged commit 1703e59 into lf-edge:master Mar 9, 2026
50 checks passed
@rucoder rucoder added the stable Should be backported to stable release(s) label Mar 24, 2026
@europaul
Copy link
Copy Markdown
Contributor

16.0-stable: yes
14.5-stable: yes ifzks is available
13.4-stable: No

@rucoder we need to backport to all those branches since the new version of linuxkit doesn't allow us to use those fields and we're updating to new linuxkit everywhere

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

stable Should be backported to stable release(s)

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants