Problems with the DEVNOTES instructions

[divSelector]

Hi, I found your project today and am interested in playing with it.

This command is in DEVNOTES.MD:

docker exec -i $(docker ps | grep postgres | awk '{ print $1 }') psql -U iss_user -v -d iss < seed-data.sql

This command will fail if docker ps | grep postgres | awk '{ print $1 }' returns more than one container, say for example if there is another project with a postgres container on the dev machine. You can easily get around it though by just getting the container ID manually.

While I am familiar with Django and Docker, I'm not familiar with the tools you're using for the frontend.

I get these errors

statics-1  | [23:08:40] Using gulpfile ~/static-builder/gulpfile.js
statics-1  | [23:08:40] Starting 'watch'...
statics-1  | [23:08:40] Starting 'generate'...
statics-1  | [23:08:40] Starting 'less'...
statics-1  | [23:08:40] Starting 'smilies'...
statics-1  | [23:08:40] Starting 'jpgs'...
statics-1  | [23:08:40] Starting 'javascript'...
statics-1  | [23:08:40] Starting 'icons'...
statics-1  | (node:19) DeprecationWarning: sprintf() will be removed in the next major release, use the sprintf-js package instead.
statics-1  | (Use `node --trace-deprecation ...` to show where the warning was created)
statics-1  | [23:08:40] 'smilies' errored after 77 ms
statics-1  | [23:08:40] Error: EACCES: permission denied, mkdir '/home/node/static-builder/dist/img/gif'
statics-1  | [23:08:40] 'generate' errored after 78 ms
statics-1  | [23:08:40] 'watch' errored after 81 ms
statics-1 exited with code 1

The result is that the app starts up with the correct data but there is no static files

I'll play around it with it and see if I can figure it out, but I thought I'd let you know about the issues I encountered so far following the instructions.

[divSelector]

So what I did to get a little further...

docker compose -f docker-compose.dev.yml run --rm statics /bin/bash

I opened up a shell in the container to try to see if I could make the directory '/home/node/static-builder/dist/img/gif'

as expected, no permissions.

I look in the docker file and find the volumes

  statics:
    build:
      context: .
      target: statics
    command: npm run watch -- --out-dir=./dist
    volumes:
      - ./src/statics/src:/home/node/static-builder/src
      - ./src/ISS/static:/home/node/static-builder/dist

I check into ./src/ISS/static and find that there is an img directory but no img/gif so I make it.

This time I get a similar issue

statics-1  | [00:21:43] 'smilies' errored after 78 ms
statics-1  | [00:21:43] Error: EACCES: permission denied, open '/home/node/static-builder/dist/img/gif/RisiR.gif'

I'll have to do some more poking around to figure out where it's getting that filename from.

[divSelector]

Local machine

 ls -ld ./src/ISS/static ./src/ISS/static/img 
drwxrwxr-x 4 user user 4096 Jul 23 17:24 ./src/ISS/static
drwxrwxr-x 2 user user 4096 Jul 23 19:45 ./src/ISS/static/img

statics container

node@befc6c121ebc:~/static-builder$ ls -ld ./ ./dist/
drwxr-xr-x 1 node node 4096 Jul 23 22:22 ./
drwxrwxr-x 4 root root 4096 Jul 23 22:24 ./dist/

So it's mounting the volume with the wrong permissions which is why it can't do anything. I'm not sure what to do about that but I'll think on it.

[divSelector]

I brute forced everything I could think of to get it to work. It does work though.

I changed your Dockerfile to

FROM node:18 AS statics

USER root

WORKDIR /home/node/static-builder
COPY ./src/statics ./

RUN npm ci
RUN npm run build

RUN chown -R node:node /home/node/static-builder/dist

I have no idea if this is a bad practice or might break something else though.

[Lanny]

Hi there. Sorry for the delay getting back to you and thank you for trying out ISS! Good call on the first issue with multiple postgres images running. I updated to command to use the container name which includes "iss" so hopefully this is less prone to conflict.

[Lanny]

On the second issue, I'm trying to figure out what's going on here. This doesn't happen for me, looking around the internet it seems like there are some distinctions on how the permissions of the container work based on your docker runtime and "rootless" mode, I'm not able to reproduce the issue although I would like to fix it if possible. Could you try adding:

    user: root

into the statics service block in docker-compose.dev.yml and let me know if you're still experiencing the same issue or if that fixes it? I'd like to avoid having to build the statics as root, but can live with running the statics file watcher as root in a development context (although ideally there would be a mechanism to do a bind mount and specify the in-container owner of it, but I guess not depending on runtime?)