Docker install fails - mv cannot move to subdirectory of itself

Technical Help
,
1

Are you using our SaaS platform (Baserow.io) or self-hosting Baserow?

Self-hosted

If you are self-hosting, what version of Baserow are you running?

baserow version 1.32.5

If you are self-hosting, which installation method do you use to run Baserow?

Docker version 28.0.4
On a debian 11.11 LXC container
On a proxmox 7.4 physical host

What are the exact steps to reproduce this issue?

See description in topic : Baserow docker container - Error on startup - Cannot "mv" file - #12 by olgatrykush

Steps :

  1. Install docker
  2. Launch container with the one-liner : docker run \ -d \ --name baserow \ -e BASEROW_PUBLIC_URL=http://localhost \ -v baserow_data:/baserow/data \ -p 80:80 \ -p 443:443 \ --restart unless-stopped \ baserow/baserow:1.32.5
  3. Container is restarting in loop, Observe the error message : mv: cannot move '/baserow/supervisor/includes/disabled/embedded-postgres.conf' to a subdirectory of itself, '/baserow/supervisor/includes/enabled/embedded-postgres.conf'
  4. Re-try with an added -e DATABASE_URL=postgresql://user:pwd@host:port/db to the command.
  5. See the same failure, with a slightly different error mv: cannot move '/baserow/supervisor/includes/disabled/embedded-redis.conf' to a subdirectory of itself, '/baserow/supervisor/includes/enabled/embedded-redis.conf'

Thanks for any help !

2

Hi @EliasMM,

unfortunately I cannot reproduce this issue and the last answer there from the user with the similar issue was:

It must’ve been some OS related error that we couldn’t track down

I’m not entirely sure how I can help here, but this error suggests there’s a filesystem issue inside your Baserow Docker container. The system is trying to move configuration files but fails because it considers the destination to be a subdirectory of the source — which shouldn’t be the case.

One approach could be to open a shell inside the container and verify whether it’s actually possible to move files between those folders, and check if any of them are symlinks pointing to each other.

3

Thanks for looking into it. Unfortunately I cannot test that, as the container keeps restarting and docker won’t attach.

Guess I’ll go the VM way then, to have a clean start !