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

On my arm64 machine, I cannot start a multi-process container #580

Open
Wnthr opened this issue Jan 19, 2024 · 1 comment
Open

On my arm64 machine, I cannot start a multi-process container #580

Wnthr opened this issue Jan 19, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@Wnthr
Copy link

Wnthr commented Jan 19, 2024

Version
Docker image versions I have tried: pulp/pulp:latest, pulp/pulp:stable, pulp/pulp:3.42

Describe the bug
When doing a docker run, it exits immediately, and the logs show the following:

/init: line 37: /command/s6-overlay-suexec: cannot execute binary file: Exec format error
/init: line 37: /command/s6-overlay-suexec: Success

To Reproduce
docker pull pulp/pulp
$ docker run --detach
--publish 8080:80
--name pulp
--volume "$(pwd)/settings":/etc/pulp:Z
--volume "$(pwd)/pulp_storage":/var/lib/pulp:Z
--volume "$(pwd)/pgsql":/var/lib/pgsql:Z
--volume "$(pwd)/containers":/var/lib/containers:Z
--device /dev/fuse
pulp/pulp

Expected behavior
Docker image up and running

Additional context
I pull the image from docker hub. Other containers are running on the machine, so docker seems to be working as intended.

@mikedep333
Copy link
Member

Yeah, the pulp_ci_centos image needs logic to install s6 according to the correct architecture.

@mikedep333 mikedep333 added bug Something isn't working and removed Triage-Needed labels Jan 23, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

2 participants