Eric Huber

Sorry, I missed the earlier ping. I don't have time to put together a test case right now but I may be able to think about it later this fall....

I have a PR from last week pending here, that does add a few words describing how to turn on the "virtualization" option before the "Rosetta" option: https://github.com/PrairieLearn/PrairieLearn/pull/9802 Hopefully this...

Side note about a failed alternative: I did experiment with simply adding an additional user and group 1001:1001 to the image, and also adding this user to the `users` group...

As a stopgap until this is merged, I made a post explaining a temporary workaround that at least helps with locally testing the workspace (enabling saving and submitting): https://github.com/PrairieLearn/PrairieLearn/discussions/10250

> Maybe I misunderstood what this PR is meant to do. Is this meant to make this workspace work with native local development? Or does this just improve things for...

> Ahh, ok. I thought this was fixing some user-facing error (either locally or in prod), but really this is just about being internally consistent with what user we're running...

With this PR, we're baking in the 1001:1001 uid and gid for jovyan, so baking in 1000:1000 instead would require separate builds for local testing. On the other hand dynamic...

> For other PL workspace images, we would have to add that dynamic behavior ourselves. However there may be cases where this isn't trivial. I may go ahead and try...

> Do you already know what this would look like? @joelostblom For example, I began prototyping something where you could put this in your `info.json`: ```json "workspaceOptions": { "image": "prairielearn/workspace-jupyterlab-python",...

For now I removed the experimental uv install step (at the cost of a slower build) and perhaps the refactoring to base image or adding the custom local user features...