Following the stalemate documented in an earlier post, a clean install was attempted. Sadly, while 0.258.7 promises several improvements a fully functional server was not obtained.
The installation followed the procedure outlined in Installing NocoDB with Docker Compose with the exception that several alternative locations were attempted for the volume locations, all to no avail.
Essentially, new Bases can be created but new Tables never appear. Only an endless data spinner is obtained. Ugh!
If Table creation is repeated, an error results:
“Duplicate table alias”
Other minor issues are:
- Email setup appears incomplete even after successful tests.
- upgrade notice appears unnecessarily (0.258.7 is running):
Node: v20.15.1
Arch: x64
Platform: linux
Docker: true
RootDB: pg
PackageVersion: 0.258.7
- The message alert icon turns itself back on after page changes:
First and foremost we would like to vet the Docker Compose yml file.
# version: '2.1'
# updated YML with new volumes paths
services:
nocodb:
depends_on:
root_db:
condition: service_healthy
environment:
NC_DB: "pg://root_db:5432?u=postgres&p=password&d=root_db"
NC_ATTACHMENT_FIELD_SIZE: 2097152000
NC_PUBLIC_URL: "https://my.domain.com"
image: "nocodb/nocodb:latest"
ports:
- "8080:8080"
restart: unless-stopped
volumes:
- "~/nocodb-data/nc_data:/usr/app/data"
root_db:
environment:
POSTGRES_DB: root_db
POSTGRES_PASSWORD: password
POSTGRES_USER: postgres
healthcheck:
interval: 10s
retries: 10
test: "pg_isready -U \"$$POSTGRES_USER\" -d \"$$POSTGRES_DB\""
timeout: 2s
image: postgres:16.6
restart: always
volumes:
- "~/nocodb-data/db_data:/var/lib/postgresql/data"
volumes:
db_data: {}
nc_data: {}
Is the above a good configuration for NocoDB?
Logs are on hand if needed.
-Thank you