Unable to run Spoolman in Docker Container on MacOS

[cruiten]

Describe the bug If followed the Docker installation instructions for Spoolman, but when I try to start the container it continually reports the following errors:

I performed the "sudo chown -R 1000:1000 data" command, but that had no effect on the problem.

To Reproduce Steps to reproduce the behavior: Followed the instructions located here: https://github.com/Donkie/Spoolman?tab=readme-ov-file#docker-install

Expected behavior Expected that Spoolman application would start.

Screenshots If applicable, add screenshots to help explain your problem.

Spoolman Host (please complete the following information):

• Installation type: Docker
• Installed version: 0.19.3
• OS and Distro: MacOS 12.7.5
• Database type: SQLite

Desktop (please complete the following information):

• OS: MacOS 12.7.5
• Browser Chrome

• Additional context Add any other context about the problem here.

[cruiten]

Updated macOS to 12.7.6, but this did not resolve the problem.

[cruiten]

Oops, it appears that I closed this issue by mistake...

[RonanRaven]

Would you mind printing the permissions using ls -n data/ to make sure the permissions are correct?

Another option might be to just use a docker volume, so it would turn the compose into something like:

services:
  spoolman:
    image: ghcr.io/donkie/spoolman:latest
    restart: unless-stopped
    volumes:
      # Mount the host machine's docker volume into the container's /home/app/.local/share/spoolman directory
      # "docker volume ls" to show the volume, and a "docker volume rm <spoolman vol from ls>" to permanently remove it
      - spoolman_data:/home/app/.local/share/spoolman
    ports:
      # Map the host machine's port 7912 to the container's port 8000
      - "7912:8000"
    environment:
      - TZ=Europe/Stockholm # Optional, defaults to UTC
volumes:
  spoolman_data:

keep in mind, you'll need to delete the volume if you want to permanently remove the data. docker compose down does not remove volumes.

[cruiten]

I will do this, but it will be about two weeks until I am back at my printer...

Thanks for the response.

On Sun, Sep 1, 2024, 05:00 RonanRaven @.***> wrote:

Would you mind printing the permissions using ls -n data/ to make sure the permissions are correct?

Another option might be to just use a docker volume, so it would turn the compose into something like:

services: spoolman: image: ghcr.io/donkie/spoolman:latest restart: unless-stopped volumes:

Mount the host machine's docker volume into the container's /home/app/.local/share/spoolman directory

  # "docker volume ls" to show the volume, and a "docker volume rm <spoolman vol from ls>" to permanently remove it
  - spoolman_data:/home/app/.local/share/spoolman
ports:
  # Map the host machine's port 7912 to the container's port 8000
  - "7912:8000"
environment:
  - TZ=Europe/Stockholm # Optional, defaults to UTC

volumes: spoolman_data:

keep in mind, you'll need to delete the volume if you want to permanently remove the data. docker compose down does not remove volumes.

— Reply to this email directly, view it on GitHub https://github.com/Donkie/Spoolman/issues/441#issuecomment-2323139185, or unsubscribe https://github.com/notifications/unsubscribe-auth/AGGPPWIZXIQUNN32QWHOGH3ZUJ7L3AVCNFSM6AAAAABMKE5CF6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGMRTGEZTSMJYGU . You are receiving this because you modified the open/close state.Message ID: @.***>

[cruiten]

@RonanRaven Here is a screenshot of the ls -n command output:

FYI: Spoolman now works in Docker when I use your updated docker-compose.ymlper your instructions to use the docker volume...

Strange that I have to go through these extra steps in order to make it work... Is something not configured properly on my computer?

[cruiten]

Screenshot of ls -na, in case it might be helpful...

[criskb]

im on latest macOS version and didn't have any issues I just inspected the data folder and manually set write permissions from the options on the bottom, however im unable to get any connection from my K1 printer running Fluidd to spoolman. I can open spool man in my browser just fine