Offline Dockerized Penpot assets don't render

[Sam]

I have self-hosted the Docker (version 27.0.3) Penpot application, but I’m facing an issue where none of my assets are rendering. However, when I hover over them, they become visible temporarily.

[Alex]

Hi @Sam

It sounds like a configuration problem, when you move the cursor Penpot is rendering thumbnails of the boards not hovered (and that images seems not to be correctly rendered).

Could you please include your docker compose file?, also please include screenshots from the network console showing the failing requests

Alex

[Sam]

I’m using Ubuntu with docker, docker-compose,
this is my docker compose file:

version: “3.8”

networks:
penpot:
driver: bridge

volumes:
penpot_postgres_v15:
penpot_assets:

services:
penpot-frontend:
image: “penpotapp/frontend:latest”
restart: always
networks:
- penpot
ports:
- “9001:80”
environment:
- PENPOT_FLAGS=${PENPOT_FLAGS}
- PENPOT_PUBLIC_URI=${PENPOT_PUBLIC_URI}
volumes:
- penpot_assets:/opt/data/assets

penpot-backend:
image: “penpotapp/backend:latest”
restart: always
networks:
- penpot
volumes:
- penpot_assets:/opt/data/assets
depends_on:
- penpot-postgres
- penpot-redis
environment:
- PENPOT_FLAGS=${PENPOT_FLAGS}
- PENPOT_DATABASE_USERNAME=${PENPOT_DATABASE_USERNAME}
- PENPOT_DATABASE_PASSWORD=${PENPOT_DATABASE_USERNAME}
- PENPOT_REDIS_URI=${PENPOT_REDIS_URI}
- PENPOT_ASSETS_STORAGE_BACKEND=assets-fs
- PENPOT_STORAGE_ASSETS_FS_DIRECTORY=/opt/data/assets
- PENPOT_REGISTRATION_ENABLED=${PENPOT_REGISTRATION_ENABLED}
- PENPOT_SMTP_DEFAULT_FROM=${PENPOT_SMTP_DEFAULT_FROM}
- PENPOT_SMTP_DEFAULT_REPLY_TO=${PENPOT_SMTP_DEFAULT_REPLY_TO}
- PENPOT_SMTP_HOST=${PENPOT_SMTP_HOST}
- PENPOT_SMTP_PORT=${PENPOT_SMTP_PORT}
- PENPOT_SMTP_USERNAME=
- PENPOT_SMTP_PASSWORD=
- PENPOT_SMTP_TLS=false
- PENPOT_SMTP_SSL=false

penpot-exporter:
image: “penpotapp/exporter:latest”
restart: always
networks:
- penpot
environment:
- PENPOT_PUBLIC_URI=http://penpot-frontend
- PENPOT_REDIS_URI=redis://penpot-redis/0

penpot-postgres:
image: “postgres:15”
restart: always
stop_signal: SIGINT
networks:
- penpot
volumes:
- penpot_postgres_v15:/var/lib/postgresql/data
environment:
- POSTGRES_INITDB_ARGS=–data-checksums
- POSTGRES_DB=${PENPOT_DATABASE_DBNAME}
- POSTGRES_USER=${PENPOT_DATABASE_USERNAME}
- POSTGRES_PASSWORD=${PENPOT_DATABASE_PASSWORD}

penpot-redis:
image: redis:7
restart: always
networks:
- penpot

penpot-mailcatch:
image: sj26/mailcatcher:latest
restart: always
expose:
- ‘1025’
ports:
- “1080:1080”
networks:
- penpot

[Alex]

Could you also please include screenshots from the network console showing the failing requests?

Also, could you test customizing directly the version of the docker-compose we have here to check where the problem starts?

[Sam]

screenshots from the network console:

[Sam]

found the issue, I noticed that the frontend also has a volume to the assets, in other words, the following two lines are in the frontend and in the backend of docker-compose.yaml:

volumes:

• penpot_assets:/opt/data/assets

[Alex]

Great!, so now everything is working right, isn’t it?

[Sam]

Yes, everything is working well

[CrazyBlot]

Hello. Trying PenPot on complex project right now as an UX-designer. We uses Self-Host on Docker (details not available right now).
The same render issue strike me a lot. Can you explain more detailed how to avoid and I redirect your solution to IT.

[Sam]

In my Docker Compose file for the front-end part, I used the following line:

(yaml file)

volumes:
penpot_assets:/opt/data/assets

It was missing from my Docker Compose file.

[CrazyBlot]

Thanks! Will try! Check my local self-host anf there that string present in front-end section.