setup: Setup completely breaks docker
After ./setup.sh and docker compose up, every call to docker compose up from anywhere results in something like this:
not@important:~/streamlit-workshop$ docker compose up
[+] Running 7/0
✔ Container redash-postgres-1 Running 0.0s
✔ Container redash-redis-1 Running 0.0s
✔ Container redash-adhoc_worker-1 Running 0.0s
✔ Container redash-scheduler-1 Running 0.0s
✔ Container redash-scheduled_worker-1 Running 0.0s
✔ Container redash-server-1 Running 0.0s
✔ Container redash-nginx-1 Running 0.0s
Attaching to redash-adhoc_worker-1, redash-nginx-1, redash-postgres-1, redash-redis-1, redash-scheduled_worker-1, redash-scheduler-1, redash-server-1
redash-scheduler-1 | [2023-12-05 22:33:14,501][PID:24][INFO][Beat] Scheduler: Sending due task sync_user_details (redash.tasks.sync_user_details)
redash-scheduler-1 | [2023-12-05 22:33:14,504][PID:1][INFO][MainProcess] Received task: redash.tasks.sync_user_details[5a16ec2e-2195-464a-bd17-8cab90ca9ad7] expires:[2023-12-05 22:33:59.502083+00:00]
redash-scheduler-1 | [2023-12-05 22:33:14,506][PID:585][INFO][ForkPoolWorker-563] Task redash.tasks.sync_user_details[5a16ec2e-2195-464a-bd17-8cab90ca9ad7] succeeded in 0.000744658056647s: None
redash-scheduler-1 | [2023-12-05 22:33:22,970][PID:24][INFO][Beat] Scheduler: Sending due task refresh_queries (redash.tasks.refresh_queries)
redash-scheduler-1 | [2023-12-05 22:33:22,973][PID:1][INFO][MainProcess] Received task: redash.tasks.refresh_queries[d42edeb4-c232-4e6f-b39d-aa6649523fcc]
redash-scheduler-1 | [2023-12-05 22:33:22,975][PID:585][INFO][ForkPoolWorker-563] task_name=redash.tasks.refresh_queries task_id=d42edeb4-c232-4e6f-b39d-aa6649523fcc Refreshing queries...
redash-scheduler-1 | [2023-12-05 22:33:22,983][PID:585][INFO][ForkPoolWorker-563] task_name=redash.tasks.refresh_queries task_id=d42edeb4-c232-4e6f-b39d-aa6649523fcc Done refreshing queries. Found 0 outdated queries: []
redash-scheduler-1 | [2023-12-05 22:33:22,986][PID:585][INFO][ForkPoolWorker-563] Task redash.tasks.refresh_queries[d42edeb4-c232-4e6f-b39d-aa6649523fcc] succeeded in 0.0114565880504s: None
^CGracefully stopping... (press Ctrl+C again to force)
Aborting on container exit...
[+] Stopping 7/7
✔ Container redash-adhoc_worker-1 Stopped 3.1s
✔ Container redash-nginx-1 Stopped 1.0s
✔ Container redash-scheduler-1 Stopped 3.5s
✔ Container redash-scheduled_worker-1 Stopped 3.8s
✔ Container redash-server-1 Stopped 1.5s
✔ Container redash-postgres-1 Stopped 1.4s
✔ Container redash-redis-1 Stopped 1.1s
canceled
This project is not redash. Reinstalling docker with
sudo systemctl stop docker
sudo apt-get purge ...
sudo rm -rf /etc/docker /var/lib/docker
...
didn’t help. I’ll have to reinstall the OS on multiple servers and on my personal PC. This is completely terrible and I might get fired. Even so I hope it’s just my fault.
Issue was tested on Debian GNU/Linux 12 (bookworm) x86_64 docker version 20.10.24+dfsg1 and Pop!_OS 22.04 LTS x86_64 docker version 24.0.7. Compose upping was tested on multiple different repositories, with a similar result.
About this issue
- Original URL
- State: closed
- Created 7 months ago
- Comments: 29 (18 by maintainers)
Oh, that change to “no longer automatically add stuff to the users profile” has been merged now too. So future people using the setup script shouldn’t find their Docker Compose suddenly acting weirdly. 😉
When looking at the script today, that surprised me as well (I’m not the original author).
I’ve left that bit “as is” for now, but am seriously tempted to change that too.
Will think it over. 😉
Probably not. Just more a matter of “hmmm, I wonder why it did that…?”. 😁
No, they have Docker working perfectly fine for their Redash installation, which is what they used the script for.
It seems like your setup is installing several Docker related things on the same server. Clearly that means you need to do a bit of extra work (aka change the .profile). It seems like you’re getting bent out of shape by it, and I’m not sure why.
Anyway, I’m done arguing with you.