0.13.3

• use newer images for e2e tests
• print docker and docker-compose version at the start of a dojo run
• print debug output about local env vars

0.13.2

• fix the automated GitHub release

0.13.1

• docker-compose: support it when there is no version statement in the top of the yaml file; tested with docker-compose v2.24.5 and v2.31.0
• docker-compose: fix json decoding on mac - the Publishers field was resulting in decoding errors
• bump dojo image scripts base images
• alpine:3.21
• ubuntu:24.10

0.13.0

• Support multiple levels of log output produced by Dojo: silent, error, warn, info, debug
• Preserve log output setting into the docker containers too, to configure how much output is visible from the dojo image scripts. (You'll need to rebuild your images for this to take effect)

Log level setup example

Since this release, you now have more control over how much output you see. Default behaviour, using INFO log level:

$ ./bin/dojo --log-level=info  -c Dojofile.build 
2024/02/05 23:57:08 [ 1]  INFO: (main.main) Dojo version 0.13.0
2024/02/05 23:57:08 [17]  INFO: (main.DockerDriver.HandleRun) docker command will be:
 docker run --rm -v /encrypted/ssd/code/dojo:/dojo/work -v /home/ewa:/dojo/identity:ro -v /tmp/dojo-environment-multiline-dojo-dojo-2024-02-0523-57-08-9143870684282127602:/etc/dojo.d/variables/00-multiline-vars.sh -v /tmp/dojo-environment-bash-functions-dojo-dojo-2024-02-0523-57-08-9143870684282127602:/etc/dojo.d/variables/01-bash-functions.sh --env-file=/tmp/dojo-environment-dojo-dojo-2024-02-0523-57-08-9143870684282127602 -v /tmp/.X11-unix:/tmp/.X11-unix --security-opt seccomp:unconfined -ti --name=dojo-dojo-2024-02-0523-57-08-9143870684282127602 kudulab/golang-dojo:892ba15188ba0753d0050f293faa74b364c8beb8
05-02-2024 10:57:08 Dojo entrypoint info: Sourcing: /etc/dojo.d/variables/00-multiline-vars.sh
05-02-2024 10:57:08 Dojo entrypoint info: Sourcing: /etc/dojo.d/variables/01-bash-functions.sh
05-02-2024 10:57:08 Dojo entrypoint info: Sourcing: /etc/dojo.d/variables/50-variables.sh
05-02-2024 10:57:08 Dojo entrypoint info: Running: /etc/dojo.d/scripts/01-fail-fast.sh
05-02-2024 10:57:08 Dojo entrypoint info: Running: /etc/dojo.d/scripts/20-setup-identity.sh
05-02-2024 10:57:09 Dojo entrypoint info: Running: /etc/dojo.d/scripts/50-fix-uid-gid.sh
05-02-2024 10:57:09 Dojo 50-fix-uid-gid info: olduid == newuid == 1000, nothing to do
05-02-2024 10:57:09 Dojo entrypoint info: Running: /etc/dojo.d/scripts/90-run-user.sh
05-02-2024 10:57:09 Dojo entrypoint info: dojo init finished (interactive shell)
[05-02-2024 10:57:09]0 dojo@e5bb90386fb8(golang-dojo):/dojo/work$ exit
exit

and new behaviour, using ERROR log level:

$ ./bin/dojo --log-level=error  -c Dojofile.build 
[05-02-2024 10:57:09]0 dojo@feeba8efadb4(golang-dojo):/dojo/work$ exit
exit

0.12.1

• Fix #37 - support the case when the current directory contains special characters

0.12.0

• Compile Dojo using Golang 1.21.6 thanks to using Docker image kudulab/golang-dojo:2.1.0
• Improve support for Docker-compose >2.
• New versions of Docker-compose (e.g. 2.24.5) have different output of the docker-compose ps command (than the old versions of Docker-compose, e.g. 1.23.2). This was affecting Dojo as in Dojo was not aware that the containers were already created and running. This, in turn, was affecting the logging collection (the --print-logs options).
• Also, the default docker containers in Docker-compose >2 contain this string -default- (with dashes), while the older versions of Docker-compose contained this string _default_ (with underscores)
• Fix #35 - support the case when the current directory contains upper case letters and Docker-Compose >2 is run

0.11.0

• Compile Dojo using Golang 1.17.7 thanks to using Docker image kudulab/golang-dojo:2.0.0

0.10.5

• Update a log message in entrypoint about sourcing the scripts

0.10.4

• Fix issue #31. When using Colima instead of Docker Desktop or instead of running Docker on Linux, the output of docker-compose ps command is different. Without this fix, Dojo panics with slice bounds out of range in this line: https://github.com/kudulab/dojo/blob/0.10.3/docker_compose_driver.go#L633

0.10.3

• Add workaround for issu #27. Instead of exiting with error, ignore the error with particular message and print a log message.