search

Budibase / budibase

Low code platform for building business apps and workflows in minutes. Supports PostgreSQL, MySQL, MariaDB, MSSQL, MongoDB, Rest API, Docker, K8s, and more 🚀
https://budibase.com
Other
22.47k stars 1.55k forks source link

[BUDI-6702] budi CLI doesn't work, and doesn't produce the logs it says it does #9887

Closed dnk8n closed 1 year ago

dnk8n commented 1 year ago

Checklist

Hosting

Describe the bug budi hosting --start fails, and so does budi hosting --update)

To Reproduce Steps to reproduce the behavior:

  1. Follow docs to install, then finally: npm install -g @budibase/cli
  2. budi --version works (see below)
  3. budi hosting --init works
  4. budi hosting --start fails
  5. Logs are not written to file: docker-error.log

Expected behavior I expected a similar behavior to docker-compose up -d

Screenshots Screencast from 06-03-2023 14:35:28.webm

BUDI-6702

dnk8n commented 1 year ago

Some context / extra info, probably unrelated to this bug but interesting to know...

I can simply proceed using docker compose up -d (with either docker-compose or even with plugin version of compose, which the CLI doesn't support, my machine has both installed)

What is the value of the CLI if it all works with docker-compose under the hood? And btw, it never fully worked until I did a docker compose restart.

mike12345567 commented 1 year ago

Hi @dnk8n - I was not able to replicate this - I expect the issue is to do with the mixture of docker-compose and the newer docker compose functionality which we are waiting for support for (brought up in other issue: https://github.com/Budibase/budibase/issues/9871).

I'm currently using Docker version 20.10.14 with Docker-compose version 1.27.4 - with a clean Budi CLI install this is able to init and start the services fine.

Not sure what more can be done on this issue while we await support for the new docker compose sub-command which is documented in the other issue.

In terms of value of these commands in the CLI, the init and update commands are more use than anything else, the start and stop can be ran directly through docker compose with no issue, we just thought it would be helpful to provide a system for getting the docker-compose file and filling out the environment file with unique secrets, and updating it incase any changes have occurred to the docker-compose script (new service or environment variable).