8000 GSC signing fails with syntax error for OpenSUSE distro · Issue #236 · gramineproject/gsc · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

GSC signing fails with syntax error for OpenSUSE distro #236

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.

Sign up for GitHub

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

Jump to bottom
Open
KiranSukhavasi opened this issue Apr 1, 2025 · 3 comments · May be fixed by #237
Open

GSC signing fails with syntax error for OpenSUSE distro #236

KiranSukhavasi opened this issue Apr 1, 2025 · 3 comments · May be fixed by #237

Comments

@KiranSukhavasi
Copy link
KiranSukhavasi commented Apr 1, 2025 •
edited
Loading

Description of the problem and the error:
All the workloads fails during gsc signing with syntax error with the commit 057184c

**�[91m/bin/sh: -c: line 0: syntax error near unexpected token `&&'**

**/bin/sh: -c: line 0: `export PYTHONPATH="${PYTHONPATH:+$PYTHONPATH:}$(find /gramine/meson_build_output/lib64 -type d -path '*/site-packages')" &&       && gramine-sgx-sign       --key /gramine/app_files/gsc-signer-key.pem       --manifest /gramine/app_files/entrypoint.manifest       --output /gramine/app_files/entrypoint.manifest.sgx       ${passphrase:+--passphrase "$passphrase"}'
�[0m**

Steps to reproduce:
As per the steps mentioned in the url (https://github.com/gramineproject/gsc/tree/master/test), try to run any sample workload on suse distro, it fails after the gsc build and performing the gsc sign (./gsc sign-image ubuntu24.04-bash enclave-key.pem) with the above reported error.

Expected results:
No errors should be thrown and we should be able to to do the build and sign the image properly.

Actual result:

+ ./gsc sign-image --remove-gramine-deps python-test enclave-key.pem
Signing graminized Docker image `gsc-python-test-unsigned` -> `gsc-python-test`...
Step 1/12 : FROM gsc-python-test-unsigned as unsigned_image

 ---> 57e7da88ec58
Step 2/12 : ARG BUILD_ID

 ---> Running in e31220615265
 ---> Removed intermediate container e31220615265
 ---> 770e48d153a9
Step 3/12 : LABEL build_id=$BUILD_ID

 ---> Running in fe04956e314f
 ---> Removed intermediate container fe04956e314f
 ---> 8482ed8b8db4
Step 4/12 : COPY gsc-signer-key.pem /gramine/app_files/gsc-signer-key.pem

 ---> 2ee60ca3a936
Step 5/12 : ARG passphrase

 ---> Running in bc49a8f8b3b1
 ---> Removed intermediate container bc49a8f8b3b1
 ---> dc44b97870bd
Step 6/12 : RUN export PYTHONPATH="${PYTHONPATH:+$PYTHONPATH:}$(find /gramine/meson_build_output/lib64 -type d -path '*/site-packages')" &&       && gramine-sgx-sign       --key /gramine/app_files/gsc-signer-key.pem       --manifest /gramine/app_files/entrypoint.manifest       --output /gramine/app_files/entrypoint.manifest.sgx       ${passphrase:+--passphrase "$passphrase"}

 ---> Running in 1b7e7e3fd6b3
�[91m/bin/sh: -c: line 0: syntax error near unexpected token `&&'
/bin/sh: -c: line 0: `export PYTHONPATH="${PYTHONPATH:+$PYTHONPATH:}$(find /gramine/meson_build_output/lib64 -type d -path '*/site-packages')" &&       && gramine-sgx-sign       --key /gramine/app_files/gsc-signer-key.pem       --manifest /gramine/app_files/entrypoint.manifest       --output /gramine/app_files/entrypoint.manifest.sgx       ${passphrase:+--passphrase "$passphrase"}'
�[0m
 ---> Removed intermediate container 1b7e7e3fd6b3
Failed to build a signed graminized Docker image `gsc-python-test`.
@KiranSukhavasi KiranSukhavasi changed the title gsc build fails while signing the bash test image for suse GSC signing fails with syntax error for OpenSUSE distro Apr 2, 2025
@kailun-qin
Copy link
Contributor

@KiranSukhavasi: Thanks for reporting this issue!

@DukeDavis12: I think you might have missed updating this line:

gsc/templates/suse/Dockerfile.sign.template

Line 15 in 67d8235

{% block path %}export PYTHONPATH="${PYTHONPATH:+$PYTHONPATH:}$(find /gramine/meson_build_output/lib64 -type d -path '*/site-packages')" &&{% endblock %}

I'm curious why our internal CI didn't catch this. Shouldn't it validate all distros? cc @anjalirai-intel

@kailun-qin kailun-qin mentioned this issue Apr 3, 2025
Open
@DukeDavis12
Copy link
Contributor

#237 @KiranSukhavasi Please validate the changes.

@jinengandhi-intel
Copy link
Contributor
jinengandhi-intel commented Apr 3, 2025 •
edited
Loading

I'm curious why our internal CI didn't catch this. Shouldn't it validate all distros? cc @anjalirai-intel

Since this PR was going through multiple changes, we were only running ubuntu/debian distro tests.

@DukeDavis12 DukeDavis12 linked a pull request Apr 3, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Update PYTHON_PATH in SUSE sign template DukeDavis12/gsc
4 participants
@kailun-qin @KiranSukhavasi @DukeDavis12 @jinengandhi-intel
0