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

Unable to see the task progress during execution #611

Open
Katiyman opened this issue Nov 23, 2021 · 1 comment
Open

Unable to see the task progress during execution #611

Katiyman opened this issue Nov 23, 2021 · 1 comment

Comments

@Katiyman
Copy link

  • Task version: v3.9.0 (h1:k6ZHDqKU+NCJxN2PhHRB4gF0NSZVlRdRSbtP89pDKDA=)

  • Operating System: Windows 10

Example Taskfile showing the issue

# https://taskfile.dev

version: '3'

vars:
  GREETING: Hello, World!
  HTTP_PROXY: http://10.xxx.xx.6:8080/
  HTTPS_PROXY: http://10.xxx.xx.6:8080/

tasks:
  default:
    cmds:
      - echo "{{.GREETING}}"
    silent: false
  build:
    run: always
    silent: false
    cmds:
      - docker build -f Dockerfile . -t smservice:1 --network=host --build-arg  http_proxy={{.HTTP_PROXY}}  --build-arg  https_proxy={{.HTTPS_PROXY}}
    method: timestamp

I have just started using the taskfile, i want to use it to enable build in windows, which was not earlier possible with Makefile.
As shown above in the taskfile we are executing a docker build from the Taskfile, Dockerfile used in build is subsequently executing a Make, which executes the UTs and other activities, but o/p of those commands is not visible. This puts a limitation in debugging and understanding what is going on . The current O/P is like below:


 => [builder 41/45] COPY smService/testutils/minio-certs/private.key /root/.minio/certs/                                                          0.0s
 => [builder 42/45] COPY smService/testutils/minio-certs/public.crt /root/.minio/certs/                                                           0.0s
 => [builder 43/45] RUN pwd                                                                                                                       0.2s
 => **[builder 44/45] RUN make all CACHEBUST=$(date +%s)                                                                                          189.7s**
 => [builder 45/45] RUN chmod -R 775 pkg/mod                                                                                                     45.1s
 => CACHED [stage-1 2/9] RUN mkdir /lib64              

Dockerfile reference


# some pre activities
COPY ./build/buildProto.sh ./internal_interfaces/
COPY ./build/generateMock.sh ./src/smService
# copy minio tls certificates
COPY smService/testutils/minio-certs/private.key /root/.minio/certs/
COPY smService/testutils/minio-certs/public.crt /root/.minio/certs/

# Build the go app (smService_v2)
ARG CACHEBUST=3
RUN pwd
RUN make all CACHEBUST=$(date +%s)
RUN chmod -R 775 pkg/mod

#some post activities

i want to know if there is a way to see the o/p of the make all command executed from the Dockerfile.
TIA

@Katiyman Katiyman added the type: bug Something not working as intended. label Nov 23, 2021
@kerma kerma removed the type: bug Something not working as intended. label Dec 20, 2021
@kerma
Copy link
Contributor

kerma commented Dec 20, 2021

Hello @Katiyman! Can you please provide a minimal example which reproduces this issue? It should include a full Dockerfile with a make call.

However, I'm suspecting the issue is on Docker buildkit side. Please see https://docs.docker.com/engine/reference/commandline/build/ and --progress command line argument.

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