can it work with docker?

[j1cs]

I'm asking because the README says is broken.

[markhughes]

It sure can. The documentation about docker is outdated, my apologies! I'll spend some time over the next few days adjusting it.

[j1cs]

version: '3.8'
services:
  droppy:
    image: ghcr.io/droppyjs/droppy
    container_name: droppy
    ports:
      - '9002:8989'
    volumes:
      - '/media/storage/droppy:/files'
      - './droppy/config:/config'
    environment:
      UID: 1000
      GID: 1000
    networks:
      - web_nw
networks:
  web_nw:
    driver: bridge

[j1cs]

The error occurs on my linux pc.
Now i tried on my mac and it shows the same error.

[j1cs]

wait. deleting the

    environment:
      UID: 1000
      GID: 1000

the think is every file uploaded is part of the root user. so i have to change the owner every time when a new file is there. :/

[j1cs]

I did the following steps to see what happens

  droppy:
    image: ghcr.io/droppyjs/droppy
    container_name: droppy
    ports:
      - '9002:8989'
    volumes:
      - './droppy/docker-start.sh:/droppy/docker-start.sh'
      - '/media/storage/droppy:/files'
      - './droppy/config:/config'
    environment:
      UID: 1000
      GID: 1000
    networks:
      - web_nw

#!/bin/bash
set -x
# Droppy docker start file
#
#           .:.
#    :::  .:::::.    Droppy
#  ..:::..  :::      Made with love <3
#   ':::'   :::
#     '
#


# Determine a UID/GID otherwise default to 0
[ -z "${UID}" ] && UID=0
[ -z "${GID}" ] && GID=0

FILE="/droppy/UID-${UID}_GID-${GID}"
if [ ! -f "${FILE}" ]; then
  # echo >> /etc/xxx and not adduser/addgroup because adduser/addgroup
  # won't work if uid/gid already exists.
  echo -e "droppy:x:${UID}:${GID}:droppy:/home/droppy:/bin/false" >> /etc/passwd
  echo -e "droppy:x:${GID}:droppy" >> /etc/group

  # create shadow files from /etc/passwd and /etc/group
  grpconv
  pwconv

  # it's better to do that (mkdir and chown) here than in the Dockerfile
  # because it will be executed even on volumes if mounted.
  mkdir -p /config
  mkdir -p /files

  mkdir -p /home/droppy/.droppy

  ln -s /config /home/droppy/.droppy/config
  ln -s /files /home/droppy/.droppy/files

  chown -R droppy:droppy /home/droppy

  chown -R droppy:droppy /config
  chown droppy:droppy /files

  export HOME=/home/droppy

  volta install node

  touch "${FILE}"
fi
which node
exec /bin/su droppy -s /bin/bash -c "node /droppy/packages/cli/lib/cli.js start"

droppy  | /root/.volta/bin/node
droppy  | + exec /bin/su droppy -s /bin/bash -c 'node /droppy/packages/cli/lib/cli.js start'
droppy  | bash: node: command not found

as the script is being executed by root volta installs node inside in the root folder (/root/.volta/bin/node). then when the normal user (droppy in this case) tries to run app he can't because you don't have permissions.
I don't know the best solution for a non-root user to be able to run droppy and write files inside the volumes.

[markhughes]

Great find! Thanks! I will resolve this for us :)