Error in File field

Technical Help
2

I “solved” my problem by changing folder permissions. But I am unsure why this was required in the first place, and I am wondering if I did the appropriate thing.

For reference, here is my docker compose stack in Portainer:

version: '3.3'
services:
    baserow:
        container_name: baserow
        network_mode: bridge
        environment:
            - 'BASEROW_PUBLIC_URL=http://192.168.86.200:9988'
        volumes:
            - '/volume2/docker/baserow/data:/baserow/data'
        ports:
            - '9988:80'
        restart: unless-stopped
        image: 'baserow/baserow:1.13.1'

Just deploying that container allowed baserow to run, but gave me errors when trying to access the disk (exporting CSV file, adding any files to File fields, etc).

I solved the problem by navigating to the /baserow/data folder and running

chmod 777 *

Here is a screenshot of before and after I did the chmod. I am hoping someone will be able to tell me what I did wrong when deploying the container such that I needed to change permissions like I did.

image
image1545×1402 187 KB

I am concerned updating the container will negate or change what I have done, so ideally I’m looking for a solution that would permit me to “start again” by deleting my baserow folder (I have only test data there) and re-installing from Portainer with everything working properly, and no chmod required.

Thanks!

2 Likes