Dmitrii Kuvaiskii

@lonerapier Thanks for these interesting experiments! > Can I know the details of the machine used to build the official binaries and the process to build them? @woju should be...

I think we can close this issue. @mkow If you think that some parts are still relevant, I suggest to create a new issue then.

I'll close this PR as it seems to be not a problem for Gramine.

@anjalirai-intel Is this something we need to keep open? Looks like the problem is non-trivial to solve, and not really the Gramine fault. The workaround also seems to work (well,...

> What is confusing me about this issue is that it is working fine if I run it in `gramine-sgx`. I don't run into the missing `setresgid` warning. What's the...

I don't see anything special... Can you try running Linux PAL instead of Linux-SGX PAL? There is a switch in GSC to do this: https://gramine.readthedocs.io/projects/gsc/en/latest/#execute-with-linux-pal-instead-of-linux-sgx-pal

This error is interesting, I have never seen it before. What happens is this: 1. `gsc build` command line generates the `gsc--unsigned` Docker image. This Docker image contains the auto-generated-by-GSC...

Hm, maybe I'm mistaken, maybe it's just `entrypoint.manifest` in the unsigned version of the Docker image. Then you should check for this error `Reserved escape sequence used (line 34787 column...

> So, can I take the entrypoint.manifest and create a entrypoint.manifest.sgx by myself? Then I would be able to check which entry is causing the issue. Yes, please try this.

You should probably analyze the whole Line 6... I guess it has thousands of entries. Sorry, but I don't see any other way. I'm pretty sure some trusted file name...