Having issue with eft-utils after v2.x. release

[codematic-eas]

Hi Guys,

Having issue with eft-utils after v2.x. When our auto-scaling relaunch the instance recently, which failed to run certain command, but they were working before.

From the cloud-init log, I can see following error:
_Building efs-proxy

• cd src/proxy
• cargo build --release --manifest-path /tmp/efs-utils/src/proxy/Cargo.toml
  ./build-deb.sh: 33: cargo: not found_

And, I could not find the cargo from my Linux and I manually installed. When I run the script manually again, I have following error.

Error from "build-deb.sh"
+ cargo build --release --manifest-path /tmp/efs-utils/src/proxy/Cargo.toml
Compiling efs-proxy v2.0.1 (/tmp/efs-utils/src/proxy)
Building [=======================> ] 202/203: efs-proxy(bin)
error: linking with cc failed: exit status: 1

Any help is appreciated. I suspect, we need to update our script to accommodate efs-utils v2.x. But I could not find any information yet.

Thanks.
Guru

[RyanStan]

Hi Guru, can you provide the AMI or base distribution you're using? I'll attempt to re-create it.

[mskanth972]

Did you follow these Steps for building a debian pkg?
https://github.com/aws/efs-utils?tab=readme-ov-file#on-other-linux-distributions

[codematic-eas]

Hi, We set to use previous commit use the previous version for now. We yet to plan to change to v2.0 later. Sent from Outlook for Android<https://aka.ms/AAb9ysg>

…

________________________________ From: Shashi Kanth M ***@***.***> Sent: Tuesday, May 14, 2024 9:30:41 PM To: aws/efs-utils ***@***.***> Cc: codematic-eas ***@***.***>; Author ***@***.***> Subject: Re: [aws/efs-utils] Having issue with eft-utils after v2.x. release (Issue #212) Did you follow these Steps for building a debian pkg? https://github.com/aws/efs-utils?tab=readme-ov-file#on-other-linux-distributions — Reply to this email directly, view it on GitHub<#212 (comment)>, or unsubscribe<https://github.com/notifications/unsubscribe-auth/BBCUVOJ4OCSC4D26UQ6ZPJTZCIGYDAVCNFSM6AAAAABHC3SFX2VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCMJQGI2TGNZZHA>. You are receiving this because you authored the thread.Message ID: ***@***.***>

[stanislavzaletskyi]

Got the same error like above. i use debian-12 (amazon owner) AMI and I applied workaround in aws ec2 userdata script:

    curl --proto '=https' --tlsv1.2 -sSf https://sh.rustup.rs | sh -s -- -y
    cp -r /root/.cargo /home/admin/
    . "$HOME/.cargo/env"
    apt-get update
    apt install build-essential -y
    apt install pkg-config -y
    apt-get -y install gcc
    apt-get -y install libssl-dev
    apt-get -y install git binutils
    git clone https://github.com/aws/efs-utils
    cd $WORKING_FOLDER/efs-utils
    ./build-deb.sh
    apt-get -y install ./build/amazon-efs-utils*deb

In my case it works.