We have a few known errors/situations where the output error from the final command being executed becomes misleading since the user is calling kool only. So we need to come up with some parsing for error outputs, so we can intercept and improve/make clear the error and what do to for the user.

• kool start in a folder which does not contain a project

I guess it would be nice if we improve this error message that pops out after trying to start kool on a non kool project. This message isn't following the standards of kool.

Originally #326

• kool start when there are orphan containers

Eu removi um container do docker-compose e ao rodar o kool start eu recebo essa mensagem:

O problema que fica a impressão que o usuário deveria rodar o comando: kool start --remove-orphans

E ao fazer isso eu recebo:

Originally #188

• "Creating network" issue when running kool start

This error may indicate that we have a lot of docker networks created.

We can check this by running docker network ls

In order to solve this, we can run docker network prune

And as result, we can check again:

Originally #189

• Error when trying to connect in address already in use

This error can be caused when we are trying to connect to an occupied port.

One way to resolve this is to stop running softwares that may be using these ports, such as Apache.
But we can also solve this issue using another port that is probably available.
We can force Kool to do this by adding these constants to the end of the .env file in your project:

KOOL_APP_PORT=8080
KOOL_DATABASE_PORT=13306

Like this: