Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Changing pool image from ubuntu-22.04 to ubuntu-20.04 for FunctionsNetHost Linux artifact #2653

Merged
merged 1 commit into from
Aug 7, 2024

Conversation

kshyju
Copy link
Member

@kshyju kshyju commented Aug 7, 2024

As part of the 1ES pipeline updates, we transitioned to using Ubuntu 22.04 as the build environment for producing the FunctionsNetHost Linux artifact. However, this has resulted in an artifact that is incompatible with some of our images, which still use Debian 11. The following error occurred when attempting to start FunctionsNetHost in a Debian 11 environment:

./FunctionsNetHost: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.34' not found (required by ./FunctionsNetHost)

In this pull request, we are reverting to Ubuntu 20.04, which was our previous build environment (code here).

Bumped patch version. New version is 1.0.11

Pull request checklist

  • My changes do not require documentation changes
    • Otherwise: Documentation issue linked to PR
  • My changes should not be added to the release notes for the next release
    • Otherwise: I've added my notes to release_notes.md
  • My changes do not need to be backported to a previous version
    • Otherwise: Backport tracked by issue/PR #issue_or_pr
  • I have added all required tests (Unit tests, E2E tests)

…"BuildFunctionsNetHostLinux" job.

 - Bumping patch version. New version is 1.0.11
@kshyju kshyju merged commit 3e998f5 into main Aug 7, 2024
67 of 69 checks passed
@kshyju kshyju deleted the shkr/fnh_artifact_fix branch August 7, 2024 21:18
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