maybe problems is the wrong term, lets call it features I was missing.

  - without docker images in tasks tooling was not always the same on different machines
  - a docker image that can be used for gitlab ci
  - caching on CI systems was a huge effort, requiring to specify all .task directories and build directories
  - limited includes of other build files, no nesting or loops, making project style taskfiles not possible
  - the cwd of includes is not relative to the reference taskfile

and there are some, which are not solved yet in hammerkit, but planned:

  - detect changes in cwd during commands, for example with `cd ..`
  - a service definition, allowing to use databases with some healthchecks to detect startup delays
  - limiting cpu/memory of build steps / limiting tasks that are executed parallel by resource available