open data/temp/9744479: no such file or directory

bk85

I've found REI3 in my search for a frontend form builder for postgres and it looks great but i'm running into issues. I've installed rei3 using a portainer stack on a nuc running proxmox using the docker compose file on git as a base. I'm encountering the error "open data/temp/9744479: no such file or directory error" when trying to add an application from the repository. Manually creating an app works fine and the proper schema and tables are generated in postgres. It seems an installation error on my end, something with permissions or file structure. Can anyone point me towards a fix for this? Below is the portainer docker stack:

version: '3.8'
services:
r3_db:
container_name: r3_db
image: postgres:16
ports:
- 2647:5432
restart: unless-stopped
environment:
POSTGRES_DB: DB
POSTGRES_USER: USER
POSTGRES_PASSWORD: PASS
TZ: Europe/Amsterdam
volumes:
- /etc/docker/rei3/data_db:/var/lib/postgresql/data

r3:
container_name: r3_app
image: naielv/rei3:3.10.2
build:
context: https://github.com/r3-team/r3_docker.git#main
args:
r3_version: 3.11
r3_db_host: r3_db
r3_db_name: DB
r3_db_user: USER
r3_db_pass: PASS
r3_os_arch: x64
im_policy: /etc/ImageMagick-6/policy.xml
depends_on:
- r3_db
ports:
- "14000:80"
restart: always
volumes:
- /etc/docker/rei3/data_app:/opt/r3/data

gabriel

Hello and welcome to the forum :)

The error says that a directory that is required is not there or not accessible. In this case it´s the temp directory, though r3 requires multiple directories to work correctly - these are referenced in the config.json file (s. paths).

To fix the issue, make sure that these directories are available to the r3 service. As these contain important files, you need to make sure that they not part of the stateless container, but inside a volume or something.

bk85

Thanks for the link to the config, i didn't create the subfolders in the right location. It works as it should now. I've played around a bit in the app and you've created an amazing tool. The goal is to create a frontend for a specialist database for archaeological research. The current ancient access database really needs an update.

gabriel

bk85
The only problem could be that r3 is not built to be "just a frontend" and needs to manage its database - opposed to serve as a frontend to an existing database. If your scenario is that you want to migrate your access database to something more capable, then this should be fine :)

I am always happy to hear what people use r3 for - archaeological research is a first, as far as I know :)