Summary
I have a local-only installation of Baserow on my MacBook Pro M2. Until updating Docker Desktop yesterday, I was able to initiate Baserow with docker compose up -d. After updating, I can’t connect to Baserow despite all services reading as “Started.” I use the multi-service docker-compose.yml (not docker-compose.all-in-one.yml) and have not edited it or the variables in .env.
Technical Help Questionnaire
Have you read and followed the instructions at: *READ ME FIRST* Technical Help FAQs - #2 by nigel ?
Answer: Yes.
Self-Hosted Installation and Setup Questions
How have you self-hosted Baserow.
Self-hosted, installed and run using Docker Desktop for macOS.
What are the specs of the service or server you are using to host Baserow.
Locally on a MacBook Pro M2.
Which version of Baserow are you using.
1.25.2 and 1.30.1. (Tried solving the problem with a fresh installation.)
How have you configured your self-hosted installation?
I used the default multi-service docker-compose.yml file. I copied .env.example to .env and assigned values to SECRET_KEY, DATABASE_PASSWORD, and REDIS_PASSWORD.
What commands if any did you use to start your Baserow server?
docker compose up -d
Describe the problem
Describe, step by step, how to reproduce the error or problem you are encountering.
Until updating Docker Desktop for macOS yesterday, docker compose up [-d] worked: I was able to access Baserow at http[s]://localhost. Now, I get an “Unable to connect” error in the browser, despite all services being “Started.” In the output of docker compose up, I see the following errors:
caddy-1 | Error: adapting config using caddyfile: parsing caddyfile tokens for 'on_demand_tls': the on_demand_tls 'interval' option is no longer supported, remove it from your config, at /etc/caddy/Caddyfile:4
caddy-1 exited with code 1
celery-export-worker-1 | [2025-01-10 07:04:35,911: ERROR/ForkPoolWorker-8] Task baserow.core.tasks.sync_templates_task[…] raised unexpected: ProgrammingError('relation "builder_mainthemeconfigblock" does not exist\nLINE 1: DELETE FROM "builder_mainthemeconfigblock" WHERE "builder_ma...\n ^\n')
A fresh installation using the single-image docker-compose.all-in-one.yml works:
git clone https://gitlab.com/baserow/baserow.git
cd baserow
docker compose -f docker-compose.all-in-one.yml up
but doesn’t have access to my database.
In the same freshly-installed directory, docker compose up gives the same errors as above, even with .env filled out with the same values that were working until yesterday.
Downgrading Docker Desktop didn’t help.
I don’t want to completely uninstall Docker because I have data in unbacked-up volumes.
Provide screenshots or include share links showing:
Unable to log in to Baserow.
How many rows in total do you have in your Baserow tables?
Unable to log in to Baserow.
Please attach full logs from all of Baserow’s services
Errors excerpted above.
Thanks for your attention.