as I can tell, the corresponding path does not need to exist in the container,
indeed. (that property is mentioned, or should I say, hidden in https://apptainer.org/docs/user/main/bind_paths_and_mounts.html#bind-example... ) that's a strange behaviour for a mount, but probably a reasonable choice for a container. then you just have to be sure that you're not bind-mounting to a container directory that _does_ exist (because the mount will shadow the existing files in that directory) E.g., my executable is in /app, so ... $ docker run -v ./data:/app:Z,ro --rm -it jwaldmann/termcomp2025-mbox:21-07-2025 solver --name docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: exec: "solver": executable file not found in $PATH J.