Mads Jon Nielsen

I have no experience with testing my Gitlab CI/CD pipeline jobs like this. You could run gitlab-ci-local remotely on a shell-executor, and develop some sort of wrapper application that parses...

I'm releasing tonight properly. I've never actually run gitlab-ci-local via gitlab ci/cd. The shell executors we use is 100% default setup via gitlab-runner register --shell

@jg-cantaa https://github.com/firecow/gitlab-ci-local/releases/tag/4.28.1 Can you try out this version please, and reopen if the bug still persists. Works on my machine, with 4.28.1

@jg-cantaa Hmm.. Why the hell can't I reproduce this... What docker version are you running ?

@jg-cantaa ```yml --- test: needs: [] image: name: gcr.io/kaniko-project/executor:debug entrypoint: [""] script: - | cat ${CI_PROJECT_DIR}/Dockerfile FROM ubuntu EOF - >- /kaniko/executor --context "${CI_PROJECT_DIR}" --dockerfile "${CI_PROJECT_DIR}/Dockerfile" --no-push ``` Can you...

> Yes it does, but that kind of defeats the purpose of using gitlab-ci-local. It should just work. It should not require --force, since a normal docker container also does...

 This is mine @jg-cantaa @bcouetil Can you try running the `test:` job from above as well

@jg-cantaa That's what I'm wondering

Do you have `.gitlab-ci-local-env` or `.gitlab-ci-local.yml` located in CWD @jg-cantaa ?

@jg-cantaa Ok, make a new dir, and only put a `.gitlab-ci.yml` with the `test:` inside and call `gitlab-ci-local test` Just so we are 2000% sure nothing file/folder specific is fucking...