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

Interactive mode doesn't work with --buildkit-host #1492

Open
jazzdan opened this issue Dec 9, 2021 · 2 comments
Open

Interactive mode doesn't work with --buildkit-host #1492

jazzdan opened this issue Dec 9, 2021 · 2 comments
Labels
type:enhancement Small feature requests / adjustments

Comments

@jazzdan
Copy link
Contributor

jazzdan commented Dec 9, 2021

With an Earthfile like this:

FROM alpine
main:
  RUN false

Without --buildkit-host it works:

$ earthly -i +main
 1. Init πŸš€
β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”

           buildkitd | Found buildkit daemon as docker container (earthly-buildkitd)


 2. Build πŸ”§
β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”

              alpine | --> Load metadata linux/arm64
               +base | --> FROM alpine
               +base | [β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ] 100% resolve docker.io/library/alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300
               +main | --> RUN false
               +main | Command /bin/sh -c false failed with exit code 1
               +main | Entering interactive debugger (**Warning: only a single debugger per host is supported**)
               +main |

/ # echo hi
hi

With --buildkit-host:

$ earthly --platform=linux/amd64 --buildkit-host tcp://earthly.dmiller.replay.local:8372 --no-output +main
 1. Init πŸš€
β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”
 2. Build πŸ”§
β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”β€”
              alpine | --> Load metadata linux/amd64
               +base | platform=linux/amd64
               +base | --> FROM alpine
               +base | [β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ] 100% resolve docker.io/library/alpine@sha256:21a3deaa0d32a8057914f36584b5288d2e5ecc984380bc0118285c70fa8c9300
               +base | [β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ] 100% sha256:59bf1c3509f33515622619af21ed55bbe26d24913cedbca106468a5fb37a50c3
               +base | [β–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆβ–ˆ] 100% extracting sha256:59bf1c3509f33515622619af21ed55bbe26d24913cedbca106468a5fb37a50c3
               +main | platform=linux/amd64
               +main | --> RUN false
               +main | Command /bin/sh -c false failed with exit code 1
               +main |
               +main | ERROR: Command exited with non-zero code: RUN false
============================ ❌ FAILURE [2. Build πŸ”§] ============================
Repeating the output of the command that caused the failure
               +main *failed* | platform=linux/amd64
               +main *failed* | --> RUN false
               +main *failed* | Command /bin/sh -c false failed with exit code 1
               +main *failed* |                +main *failed* | ERROR: Command exited with non-zero code: RUN false
Error: build target: build main: bkClient.Build: failed to solve: process "/bin/sh -c PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin /usr/bin/earth_debugger /bin/sh -c 'false'" did not complete successfully: exit code: 1
@vladaionescu
Copy link
Member

Oh yeah.. it's a known issue, but not documented. Thanks for raising this. At the very least we should fail more gracefully, saying that this isn't supported yet.

@vladaionescu vladaionescu added the type:enhancement Small feature requests / adjustments label Dec 9, 2021
@alexcb
Copy link
Collaborator

alexcb commented Dec 9, 2021

I added a more clear error under #1496 until we get a proper implementation for this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type:enhancement Small feature requests / adjustments
Projects
Status: No status
Development

No branches or pull requests

3 participants