hey everyone! I'm having fun using `pants` in ange...
# general
f
hey everyone! I'm having fun using
pants
in anger in our setup here. I had a question about the verbosity of pants when it gets to a docker build command. I'm currently running:
Copy code
$ pants --no-dynamic-ui package --docker-build-verbose //projects/thing::
which is better than no extra args, but i still get to the docker build phase of our project where i see:
Copy code
10:23:08.22 [INFO] Starting: Building docker image .../projects/thing/thing-image:398de3074947ae6865ddd296ef7484d34433050c82c78adc727d78bcf59b4bb1 +9 additional tags.
10:24:38.08 [INFO] Long running tasks:
  89.86s        Building docker image .../projects/thing/thing-image:398de3074947ae6865ddd296ef7484d34433050c82c78adc727d78bcf59b4bb1 +9 additional tags.
...
where what im interested in is why this docker build is taking so long and so what is happening in the
docker build
... i.e. those
+9 additional tags
I can (kinda?) get around this if i force pants to keep the sandbox, then try to run the docker build myself from inside the sandbox..and there i can see the actual steps and what is slow, what isn't etc but is there a way to force pants to spit out the raw-est of raw outputs and just show me everything that is happening?
b
did you try to run it with:
Copy code
pants --print-stacktrace -ldebug <rest of your command>
f
giving that a go
the interesting thing is all the things i've tried do indeed make everyting before the docker command be much much louder haha 😄 but then the docker command itself seems to quiet down 🙂 running with what you suggested though shall let you know
ah hah ok... it printed the docker command it's running... now the output is hidden still...but maybe i can now see why
hah ok... so it gives me the docker command it's apparently running...but i use that json to reconstruct that command and run from the sandbox, and THERE i see the whole output, like a normal
docker build
but still in the pants command the output is hidden
it also seems to have an env, maybe the reason is the env
ah haha 😄 the message it's giving me is literally in the env vars:
Copy code
description: "Building docker image ... +9 additional tags."
what the hell
h
Isn’t that message from Docker itself?