busybox | BusyBox for Android

How do I get -e / errexit to work in bash functions, so that the first failed command* within a function causes the function to return with an error code (just as -e works at top-level).

* not part of boolean expression, if/elif/while/etc etc etc

I ran the following test-script, and I expect any function containing f in its name (i.e. a false line in its source) to return error-code, but they don't if there's another command after. Even when I put the function body in a subshell with set -e specified again, it just blindly steamrolls on through the function after a command fails instead of exiting the subshell/function with the nonzero status code.

I get the same result in all of these envs/shells, which is to be expected I guess unless one was buggy.

Arch:

• bash test.sh (bash 5.1)
• zsh test.sh (zsh 5.8)
• sh test.sh (just a symlink to bash)

Alpine:

• docker run -v /test.sh:/test.sh alpine:latest sh /test.sh (BusyBox 1.34)

Ubuntu:

• docker run -v /test.sh:/test.sh ubuntu:21.04 sh /test.sh
• docker run -v /test.sh:/test.sh ubuntu:21.04 bash /test.sh (bash 5.1)
• docker run -v /test.sh:/test.sh ubuntu:21.04 dash /test.sh (bash 5.1)

I have the following Dockerfile:

I'm planning to move away from Docker to Podman. I use docker-compose a lot so am planning to switch to podman-compose as well.

However I'm stuck at the simplest of podman examples, I can't seem to mount a volume onto my container? Obviously I'm doing something wrong however I cant figure out what it is.

My source file definitely exists on my (hardware) host (so not the podman machine). but I keep getting the error 'no such file or directory'.

Funny thing is if I manually create the same file locally on the podman machine (podman machine ssh --> touch /tmp/test.txt) it works perfectly fine.

Question is;

• should I (manually?) mount all my local files onto the Fedora VM (podman machine) so that in turn this Fedora mount can be used in my actual container? and if so, how do I do this?
• The podman run cmd below should work and there is something else I'm doing wrong?

I am using Azure Kubernetes Services with K8S version 1.20.9 and have following K8S deployment

Version 1:

I am trying to build image for linux/arm64/v8 on linux/amd64 Gitlab runner. I run it with this command:

We want to use Paketo.io / CloudNativeBuildpacks (CNB) GitLab CI in the most simple way. Our GitLab setup uses an AWS EKS cluster with unprivileged GitLab CI Runners leveraging the Kubernetes executor. We also don't want to introduce security risks by using Docker in our builds. So we don't have our host’s /var/run/docker.sock exposed nor want to use docker:dind.

We found some guides on how to use Paketo with GitLab CI like this https://tanzu.vmware.com/developer/guides/gitlab-ci-cd-cnb/ . But as described beneath the headline Use Cloud Native Buildpacks with GitLab in GitLab Build Job WITHOUT Using the GitLab Build Template, the approach relies on Docker and pack CLI. We tried to resemble this in our .gitlab-ci.yml which looks like this:

I had a project that wanted to update the DNS configuration of Pod with Operator,

I've setup container images builds in kubernetes using kaniko (version v1.6.0-debug), but I ended up in the following problem when the cache is enabled (/kaniko/executor --cache --cache-repo $CI_REGISTRY_IMAGE/cache).

This is a simplified Dockerfile that explains the issue (the real one has a PHP package.json and package.lock files where new requirements have been added).

I have a Dockerfile