You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I recently set up Jetez on a new development environment and got this error when installing extensions I packaged with it:
[email protected]> request system software add /tmp/just-braceroute-x86-64-5.tgz
Verified just-braceroute-x86-64-5 signed by /C=US/ST=Washington/L=Redmond/O=Microsoft/OU=Azure-Networking/CN=microsoft-moby/[email protected] method RSA2048+SHA256
/packages/mnt/just-braceroute64-a92f6218/pkg/manifest: 5: invalid manifest keyword at 1
skipping to next fingerprint
The package files do get installed, but when I run the installed binary it gives me this error: ./braceroute: Authentication error.
I noticed that the file in the error message had program_id=1 on line 5, so I looked through the JetEZ commits and installed commit 1868f03, which is the one right before commit 3f975fd - "Add program_id by default."
This fixed the issue for me and now I can package extensions again, so it seems that some change after that was a breaking change for us.
Do we need to use an updated version of veriexec perhaps? The one I am using is called veriexec-x509-x86-64-20.1R20200423_1912_builder.tgz that I got from our team's Juniper contact.
The text was updated successfully, but these errors were encountered:
I recently set up Jetez on a new development environment and got this error when installing extensions I packaged with it:
The package files do get installed, but when I run the installed binary it gives me this error:
./braceroute: Authentication error.
I noticed that the file in the error message had
program_id=1
on line 5, so I looked through the JetEZ commits and installed commit 1868f03, which is the one right before commit 3f975fd - "Add program_id by default."This fixed the issue for me and now I can package extensions again, so it seems that some change after that was a breaking change for us.
Do we need to use an updated version of veriexec perhaps? The one I am using is called veriexec-x509-x86-64-20.1R20200423_1912_builder.tgz that I got from our team's Juniper contact.
The text was updated successfully, but these errors were encountered: