My situation is a a bit to try to understand how internally tutor dockerization is done and try in future to improve it.
I will explain:
I was running a tutor local instance on a WSL with ubuntu 22.04 LTS, so host Windows 11.
Such instance was been run after have set the env variable diffent from default
TUTOR_ROOT
TUTOR_PLUGINS_ROOT
MFE_ROOT
and TUTOR_APP=”my_local”
As I know, by default any tutor local or tutor dev if those above not specified it assume the ./local.
Here the situation, I have as mentioned spefied those env variable but unfortunately my Windows OS decided to update thuse shutting down all everything before to restart.
Once I restarted the WSL my tutor was was still up but in a previous old chaced state, I know this because some previous css.
Then I reset those env variable and tutor local status give me that no container was up, but as mentioned an instance is up.
Also
tutor local stop
is not stopping nothing.
I have of course made sure that the browser cache is cleaned.
No the question, in such situation which one is the best approach?
Shouldn’t tutor local stop, stop all tutor istance?
P.S I just run
tutor local start -d
and indeed I got following error:
“Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint unibo_local_local-caddy-1 (c79997948ac9db9a2605e06bd655218bdf1496d37c204a49dc23752e427ac74c): Bind for 0.0.0.0:80 failed: port is already allocated
Error: Command failed with status 1: docker compose -f /home/ca/unibo-tutor/env/local/docker-compose.yml -f /home/ca/unibo-tutor/env/local/docker-compose.prod.yml -f /home/ca/unibo-tutor/env/local/docker-compose.override.yml --project-name unibo_local_local up --remove-orphans -d”
Of course I can clean up the port but spinning another system I think would cause some other conflict between services that use same ports