Container configuration error when building codespace on Github

[Derek Thuecks]

Good morning.

PreTeXt and Github were working fine for me yesterday. This morning, I received an error upon opening my codespace.

I tried re-building the container to no effect. I also went to https://github.com/PreTeXtBook/pretext-codespace to build a new repository, but I received the same error upon my attempt to open a codespace.

I've attached the creation.log file associated with my attempt on the newly-created repository. Would anyone be able to help?

Thanks!

Derek Thuecks

[Charilaos Skiadas]

For what it's worth I also was unable to start a codespace from the pretext-codespace repository. But I didn’t even reach the stage where I could see a log. I am able to activate one of my existing codespaces.

Looking at your log the only suspicious thing is a reference to a SHA1 being considered no longer sufficient since a policy change in February 1st, so this might be related. But you said everything was working fine yesterday, so I don’t know.

It might be somehow related to the problems with GitHub actions and codespaces that were going on yesterday. 

Here’s the pertinent error from that log as far as I can tell:

1.302   Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-01-23T18:12:38Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z

1.334 Get:6 http://deb.debian.org/debian trixie-updates/main amd64 Packages [5412 B]

1.337 Get:7 http://deb.debian.org/debian-security trixie-security/main amd64 Packages [98.8 kB]

2.479 W: OpenPGP signature verification failed: https://deb.nodesource.com/node_22.x nodistro InRelease: Sub-process /usr/bin/sqv returned an error code (1), error message is: Signing key on 6F71F525282841EEDAF851B42F59B5F99B1BE0B4 is not bound:            No binding signature at time 2026-01-23T18:12:38Z   because: Policy rejected non-revocation signature (PositiveCertification) requiring second pre-image resistance   because: SHA1 is not considered secure since 2026-02-01T00:00:00Z

2.479 E: The repository 'https://deb.nodesource.com/node_22.x nodistro InRelease' is not signed.

2.482 ERROR: Feature "GitHub CLI" (ghcr.io/devcontainers/features/github-cli) failed to install! Look at the documentation at ********/devcontainers/features/tree/main/src/github-cli for help troubleshooting this error.

Charilaos Skiadas
Department of Mathematics
Hanover College

On Feb 4, 2026, at 9:46 AM, Derek Thuecks <derek....@gmail.com> wrote:

Good morning.

PreTeXt and Github were working fine for me yesterday. This morning, I received an error upon opening my codespace.

<error-message.png>

I tried re-building the container to no effect. I also went to https://github.com/PreTeXtBook/pretext-codespace to build a new repository, but I received the same error upon my attempt to open a codespace.

I've attached the creation.log file associated with my attempt on the newly-created repository. Would anyone be able to help?

Thanks!

Derek Thuecks

--
You received this message because you are subscribed to the Google Groups "PreTeXt support" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pretext-suppo...@googlegroups.com.
To view this discussion visit https://groups.google.com/d/msgid/pretext-support/3724638a-fb74-4789-8395-1b357c642d6cn%40googlegroups.com.
<error-message.png><creation.log>

[Oscar Levin]

It definitely looks like there is an error with the docker container the codespace uses.  I'm looking for a fix and will reply here when I find one.

To view this discussion visit https://groups.google.com/d/msgid/pretext-support/C20DD3A7-7F30-4D86-A56B-8CCB6AA30944%40gmail.com.

[Oscar Levin]

The pretext-codespace repository has been updated so if you make a new repository from that template, the codespace should work again.  

[Derek Thuecks]

That worked! I created a new repository, grabbed the devcontainer.json and installPandoc.sh files, placed them in the appropriate folder in my existing project repository, and started a new codespace. All is working great now.

Thanks for this and all of your work on the PreTeXt tools, Oscar!

Derek