Upgrade to Resonant v0.50.3

[brianhelba]

No description provided.

[brianhelba]

Is this still necessary, or does the migration handle it?

[brianhelba]

Modifying the volume mounts like this isn't really compatible with dev containers. Of course, it's possible to modify the Docker Compose files and then restart the whole stack, but I think the better approach is just to hardlink the files from their host filesystem into the repo.

@BryonLewis Can you test if hardlinks work, then we can update these docs accordingly?

[brianhelba]

@BryonLewis @naglepuff This is ready for testing and review. Any feedback is welcome.

[brianhelba]

I just rebased this and bumped it with an upstream patch version.

[brianhelba]

Doesn't work unless we bind to 0.0.0.0.

[brianhelba]

Test breakpoints weren't working for Bryon for some reason.

[BryonLewis]

So I decided to test this in MacOS to see how it functioned and below are some minor notes:

I modified the platform: linux/amd64 for django and celery for the Large Image wheels support so it will use Rosetta 2 translation layer.

I then removed all of my previous images and volumes for a fresh install.

I'm getting an npm access error:

npm error code EACCES
npm error syscall open
npm error path /home/vscode/pkg-cache/npm/_cacache/tmp/825561c2
npm error errno -13
npm error
npm error Your cache folder contains root-owned files, due to a bug in
npm error previous versions of npm which has since been addressed.
npm error
npm error To permanently fix this problem, please run:
npm error   sudo chown -R 1000:1000 "/home/vscode/pkg-cache/npm"
npm error Log files were not written due to an error writing to the directory: /home/vscode/pkg-cache/npm/_logs
npm error You can rerun the command with `--loglevel=verbose` to see the logs in your terminal

Exec-ing into the container and checking the folder:

$ pwd
/home/vscode/pkg-cache
$ ls -la
total 24
drwxr-xr-x 5 vscode vscode 4096 Apr 15 21:23 .
drwxr-x--- 1 vscode vscode 4096 Apr 15 21:23 ..
drwxrwxr-x 4 root   root   4096 Apr 15 21:23 npm
drwxr-xr-x 8 vscode vscode 4096 Apr 15 21:24 uv
drwxr-xr-x 4 vscode vscode 4096 Apr 15 21:23 uv-python

Looks like something is running during initialization that is writing to root access in the npm folder.

I know you have a comment in there about the User being set up in the docker file but I did try adding
"remoteUser": "vscode" to the devcontainer.json and it seems to still have this issue.

Then removed the npm command from onCreateCommand and updateContentCommand when exec-ing in there is still an npm folder in the ./pkg-cache that is owned by root. So I'm guessing it is the feature install of node:1 that is interacting with the NPM cache and some different way for MacOS rosetta that is causing problems.

To confirm the next line in this link: https://containers.dev/implementors/features/#user-env-var
States that features are typically ran as root.
I haven' parsed all of the node:1 install script but I'm guessing somethong is happening where the npm cache being set by the environment variable is initializing to root and causing problems. Weird I didn't see it in linux though.
https://github.com/devcontainers/features/blob/main/src/node/install.sh

If I exec in and delete npm cache all subsquent runs until a rebuild of the base image seem to be fine.