Hi Florian, the container needs a mount point? in order to make this work: docker run -v ./data:/mnt:Z,ro --rm -it jwaldmann/termcomp2025-mbox:21-07-2025 solver /mnt/Zantema/z001.srs You can do the mount when running (apptainer does it?) but the name "/mnt" must exist in the container? so it has to be known when building the container? (a super minimal container ("FROM scratch") might not have it) - Johannes. NB: I managed to build a nice small container (20 MB compressed - about the same size as the zip file for starexec) with the two-stage approach described here https://jpetazzo.github.io/2020/02/01/quest-minimal-docker-images-part-1/ (busybox:glibc)
Hi Johannes, I set the mount point when running the container via apptainer. As far as I can tell, the corresponding path does not need to exist in the container, so that shouldn't be an issue. Best Florian
Hi Florian,
the container needs a mount point? in order to make this work:
docker run -v ./data:/mnt:Z,ro --rm -it jwaldmann/termcomp2025-mbox:21-07-2025 solver /mnt/Zantema/z001.srs
You can do the mount when running (apptainer does it?) but the name "/mnt" must exist in the container? so it has to be known when building the container? (a super minimal container ("FROM scratch") might not have it)
- Johannes.
NB: I managed to build a nice small container (20 MB compressed - about the same size as the zip file for starexec) with the two-stage approach described here https://jpetazzo.github.io/2020/02/01/quest-minimal-docker-images-part-1/ (busybox:glibc)
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.
participants (2)
-
Florian Frohn -
Johannes Waldmann