Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Containers with different architecture from host produce confusing error #1488

Closed
markeganfuller opened this issue Apr 27, 2018 · 4 comments
Closed

Comments

@markeganfuller
Copy link
Contributor

Version of Singularity:

2.4.6-HEAD.g9ca70f5

Expected behavior

Sensible error message like:

ERROR : Container architecture is different from host.

Actual behavior

$ singularity shell test.img 
Singularity: Invoking an interactive shell within container...

ERROR  : Failed to execv() /.singularity.d/actions/shell, continuing to /bin/sh: Exec format error
ERROR  : Failed to execv() /bin/sh: Exec format error
ABORT  : Retval = 255

Steps to reproduce behavior

  • Build container on one arch, e.g. x86_64
  • Attempt to use container on another arch e.g. ppc64le
  • Error occurs
@denisovlev
Copy link

Same issue, right? #1836

What is a possible workaround for that? Only building on the same architecture?

If Singularity image is built from a docker container, does it matter what architecture this docker container was built in?

@gvallee gvallee self-assigned this Mar 29, 2019
gvallee added a commit to gvallee/singularity that referenced this issue Apr 1, 2019
…container on an hardware architecture that is not compliant.
gvallee added a commit to gvallee/singularity that referenced this issue Apr 8, 2019
@jscook2345
Copy link
Contributor

This is fixed in a newer version of singularity. Please let me know if you have any other comments or questions!

@Vishal-Joshi
Copy link

I am facing this issue where I build a docker image on my Mac M1 chip, and try to use singularity to run it on HPC nodes.

vjoshi@<some slurm node>: singularity run --bind <file_system_to_mount>:/volume docker://<image_path>:<image_label>
INFO:    Converting OCI blobs to SIF format
INFO:    Starting build...
Getting image source signatures
Copying blob 7734efb8b826 done
Copying blob bdd1baa98274 done
Copying blob 305fd4841944 done
Copying blob 81e700ced0b7 done
Copying blob 9d4a9f6bf611 done
Copying blob cd0a2bf031cd done
Copying config bc4b9c1d07 done
Writing manifest to image destination
Storing signatures
2023/12/21 12:17:39  info unpack layer: sha256:7734efb8b826f955c6a3bb51d7c84cb262d0e600ea3980f5bce69fa7f4f92d24
2023/12/21 12:17:41  info unpack layer: sha256:bdd1baa98274beac658c72b432fb0b893afa24a12f9806133933597419a299c6
2023/12/21 12:17:42  info unpack layer: sha256:305fd4841944b872966b16ccbf4bd161e200ffe17eb7c610a02aa02c025f4012
2023/12/21 12:17:49  info unpack layer: sha256:81e700ced0b7be45ce4a366b51e939e43b536c1314a0c26f402c49130917942e
2023/12/21 12:18:14  info unpack layer: sha256:9d4a9f6bf6112c07a2da4c94c5d4a05573caf5c81580c7b78fbcd3d5d3aac51a
2023/12/21 12:18:14  info unpack layer: sha256:cd0a2bf031cd03e81c2aa04b0a1fa6346849897f0f79d6904aa30b0dbe657168
INFO:    Creating SIF file...
FATAL:   could not open image /hps/scratch/singularity/vjoshi/cache/oci-tmp/b5339b9cf1158f5b9c85ddc79956f006f96ed09a19b259d30a64c9d3ab28110b: the image's architecture (arm64) could not run on the host's (amd64)

Do you have any solution to this?

@DrDaveD
Copy link
Collaborator

DrDaveD commented Dec 21, 2023

This repository is closed. If singularity --version shows singularity-ce then please create a new issue at https://github.com/sylabs/singularity, otherwise create a new one at https://github.com/apptainer/apptainer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants