docker inspect ${HOSTNAME} failed with exit status: 1 #1309
-
I'm trying to use cross within another container but I'm running into this error and I don't know what's causing it. 1 ❯ cross build --target aarch64-unknown-linux-gnu -v
+ cargo metadata --format-version 1 --filter-platform aarch64-unknown-linux-gnu
+ rustc --print sysroot
+ rustup toolchain list
+ rustup target list --toolchain stable-x86_64-unknown-linux-gnu
+ rustup component list --toolchain stable-x86_64-unknown-linux-gnu
+ /usr/sbin/docker
Error:
0: `docker inspect intellaptop` failed with exit status: 1
Stderr:
Error: No such object: intellaptop
Stdout:
[]
1 ❯ cat /etc/hostname
intellaptop
❯ env | grep CROSS
CROSS_CONTAINER_IN_CONTAINER=true Edit: Git cross version provides a little more information: cross build --target aarch64-unknown-linux-gnu -v
+ cargo metadata --format-version 1 --filter-platform aarch64-unknown-linux-gnu
+ rustc --print sysroot
+ /usr/sbin/docker
+ /usr/sbin/docker version -f '{{ .Server.Os }},,,{{ .Server.Arch }}'
+ rustup toolchain list
+ rustup target list --toolchain stable-x86_64-unknown-linux-gnu
+ rustup component list --toolchain stable-x86_64-unknown-linux-gnu
+ /usr/sbin/docker inspect intellaptop
Error:
0: `/usr/sbin/docker inspect intellaptop` failed with exit status: 1
Location:
/rustc/eb26296b556cef10fb713a38f3d16b9886080f26/library/core/src/convert/mod.rs:717
Stderr:
Error: No such object: intellaptop
Stdout:
[]
Backtrace omitted. Run with RUST_BACKTRACE=1 environment variable to display it.
Run with RUST_BACKTRACE=full to include source snippets. |
Beta Was this translation helpful? Give feedback.
Answered by
FallingSnow
Aug 13, 2023
Replies: 1 comment
-
Edit: Don't use This was caused by the hostname not being the same as the docker container's name. This should be the default so I'm not sure why it isn't happening in my case. I solved it by adding |
Beta Was this translation helpful? Give feedback.
0 replies
Answer selected by
FallingSnow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Edit: Don't use
--network host
.This was caused by the hostname not being the same as the docker container's name. This should be the default so I'm not sure why it isn't happening in my case. I solved it by adding
--hostname
to my docker run command.