Unable to Sign the graphenized Docker image using gsc sign-image: about graphene HOT 5 CLOSED

First of all, I don't know about this Avalon Docker image (avalon-python-worker-dev). I can see that the relevant page in the Avalon repo (https://github.com/hyperledger/avalon/tree/main/tc/graphene/python_worker) was last updated 7 months ago, so it may be incompatible with Graphene and GSC.

However, your steps do not seem to have any particular assumptions about Avalon and its integration with Graphene. You seem to use that Avalon Docker image as a normal input image for GSC. GSC technically should just work with any Docker image.

The error message about the "invalid character in key name" is surprising. We need to look into this deeper.

Can you peek into the gsc-avalon-python-worker-dev-unsigned Docker container using a bash session and examine the entrypoint.manifest file? If possible, you can attach this file to this GitHub issue, and maybe we can look and identify the problem. (Or you can try to do it yourself, by finding the offending TOML key.)

from graphene.

@dimakuv Please assign this to me.

from graphene.

This was actually fixed by gramineproject/gsc#10 which we just merged. I'm closing but @ntk97 please test on your side that it works now.

from graphene.

I tested with the PR [GSC] Install toml python package properly gramineproject/gsc#15, it worked

from graphene.

@ntk97 Yes, but now you can test with the master branch of GSC. I mean, you won't need to use that PR; you can just use the master now.

from graphene.