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

Adding Cross.toml with empty pre-build causes Unable to find image #1526

Open
4 of 11 tasks
nyurik opened this issue Jul 12, 2024 · 2 comments
Open
4 of 11 tasks

Adding Cross.toml with empty pre-build causes Unable to find image #1526

nyurik opened this issue Jul 12, 2024 · 2 comments

Comments

@nyurik
Copy link

nyurik commented Jul 12, 2024

Checklist

Describe your issue

Martin project uses cross to build aarch64-unknown-linux-musl and other targets, and so far worked well. Now I need to add nodejs in order to pre-build a few static resources as part of the build.rs. I added Cross.toml with [build] / pre-build = [ ... ] to configure nodejs installation, but adding even empty pre-build step causes this error:

WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load
Unable to find image 'cross-custom-martin:aarch64-unknown-linux-musl-4c595-pre-build' locally
docker: Error response from daemon: pull access denied for cross-custom-martin, repository does not exist or may require 'docker login': denied: requested access to the resource is denied.

See action run at https://github.com/maplibre/martin/pull/1416/checks - note that it simply adds "echo $CROSS_DEB_ARCH" as a pre-build step and nothing else. That PR also removes all unrelated CI steps to focus on just the failing one.

What target(s) are you cross-compiling for?

aarch64-unknown-linux-musl

Which operating system is the host (e.g computer cross is on) running?

  • macOS
  • Windows
  • Linux / BSD
  • other OS (specify in description)

What architecture is the host?

  • x86_64 / AMD64
  • arm32
  • arm64 (including Mac M1)

What container engine is cross using?

  • docker
  • podman
  • other container engine (specify in description)

cross version

cross 0.2.5

Example

No response

Additional information / notes

No response

@Emilgardis
Copy link
Member

Emilgardis commented Jul 13, 2024

The problem is actually a docker problem where after installing buildkit it does something strange with normal docker build that we use in cross 0.2.5. This was fixed in edf1e17

the real problem is this warning

WARNING: No output specified with docker-container driver. Build result will only remain in the build cache. To push result image into registry use --push or to load image into docker use --load

To resolve this, either set CROSS_BUILD_OPTS="--output=type=docker"/CROSS_BUILD_OPTS="--load" or install cross from the main branch.

@nyurik
Copy link
Author

nyurik commented Jul 13, 2024

Thx for prompt response! When do you think will be the next release?

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

2 participants