since commit b22e993224, kaniko is cgroupv2-aware.
hotfix of a34e88943a is therefore no longer needed.
Reviewed-on: #1
Co-authored-by: wanderer <wanderer@noreply.git.dotya.ml>
Co-committed-by: wanderer <wanderer@noreply.git.dotya.ml>
This is a temporary workaround that enables kaniko to run on cgroup v2
enabled hosts. Due to an upstream issue, kaniko fails to detect that it
is indeed being run from a container.
Solution introduced here is to force kaniko to run regardless.
ref: https://github.com/GoogleContainerTools/kaniko/issues/1592
* don't exit on no values provided but instead use sane defaults for
username, password and registry
* add "--no-push" flag if REPO name has not been specified
* only allow setting of TAGS if REPO has been specified as well
* rm arm/arm64/gcr/ecr related build instructions in build.sh
and .drone.ml, only build for amd64
* change autotag to manually specified tags (2 static, one dynamic)
* change the branch referenced in .drone.yml as we're using dev by
default
* module path is now git.dotya.ml/wanderer/drone-kaniko/*
