Skip to content

runc: fix how version is set after upstream change#196

Merged
pmengelbert merged 1 commit into
Azure:mainfrom
cpuguy83:fix_runc_113_version
Jun 14, 2024
Merged

runc: fix how version is set after upstream change#196
pmengelbert merged 1 commit into
Azure:mainfrom
cpuguy83:fix_runc_113_version

Conversation

@cpuguy83
Copy link
Copy Markdown
Member

Upstream changed how the binary version can be set which broke how we were setting it.
Now we can pass a VERSION env var into runcs make file to have it use that instead of modifying the VERSION file in the repo.

Because we already have a VERSION field set in the env, the runc makefile is taking that, but it does not contain the revision number, so we need to modify that env.

Upstream change that broke this is opencontainers/runc#4270

Upstream changed how the binary version can be set which broke how we
were setting it.
Now we can pass a VERSION env var into runcs make file to have it use
that instead of modifying the VERSION file in the repo.

Because we already have a VERSION field set in the env, the runc
makefile is taking that, but it does not contain the revision number, so
we need to modify that env.

Signed-off-by: Brian Goff <cpuguy83@gmail.com>
@cpuguy83 cpuguy83 requested a review from pmengelbert June 14, 2024 18:00
@pmengelbert pmengelbert merged commit 46c937c into Azure:main Jun 14, 2024
@cpuguy83 cpuguy83 deleted the fix_runc_113_version branch June 14, 2024 18:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants