#IBM PowerPC (ppc64le) support?

1 messages · Page 1 of 1 (latest)

jolly wedge
#

Hi, is it possible to run dagger on ppc64le?

I tried to install dagger cli/run the container engine on a ppc vm but seems like those binaries are missing from the builds, are there any plans to support such architecture?

jolly wedge
#

And the thing is I'm not sure how can I attempt to build both dagger cli and the dagger engine container, if I attempt to use ./hack/dev to run a local engine, it starts by downloading a dagger cli, which doesnt exist for ppc64le binary, so I can't bootstrap a development environment here

are there any docs on how to build dagger without the need of dagger cli to bootstrap?

#

Ok I managed to build the CLI (from https://github.com/dagger/dagger/blob/main/core/docs/2ku9n-getting_started.md
and set the experimental export flag

go build ./cmd/dagger

export _EXPERIMENTAL_DAGGER_CLI_BIN=$(readlink -f ./dagger)

now when running dagger cli itll automatically attempt to pull the engine image for ppc which doesnt exist in the registry

GitHub
dagger/core/docs/2ku9n-getting_started.md at main · dagger/dagger

Application Delivery as Code that Runs Anywhere. Contribute to dagger/dagger development by creating an account on GitHub.

jolly wedge
#

So I got it working and started writing the steps I used only to get blocked by discord message limit laughcry

The gist of it is adding ppc64le to internal/mage/engine.go, removing runc flags since it fails to compile only to find out its broken in final image, replacing it in a separate dockerfile using the runc binary from the official repo got it to work

I'll try to upload the complete steps as a file