Path option not working as expected

[Zethson]

Hi,

      - name: debug
        run: |
          pwd

results in /home/runner/work/mlf-core/mlf-core

My Dockerfile is in /home/runner/work/mlf-core/exploding_springfield.
It's called Dockerfile.
I verified this in the Workflow!

 cd ../exploding_springfield
  pwd
  ls -la

-rw-r--r-- 1 runner docker  528 Aug 14 16:58 Dockerfile

Hence, I expect

- name: Build Docker container
        uses: docker/build-push-action@v1
        with:
          repository: mlfcore/exploding_springfield
          tags: 0.1.0-SNAPSHOT
          push: false
          path: ../exploding_springfield

or

      - name: Build Docker container
        uses: docker/build-push-action@v1
        with:
          dockerfile: ../exploding_springfield/Dockerfile
          repository: mlfcore/exploding_springfield
          tags: 0.1.0-SNAPSHOT
          push: false
          path: ../exploding_springfield

To find the Dockerfile.
However, even with the absolute path I always run into:
unable to prepare context: path "../exploding_springfield" not found
or
unable to prepare context: path "/home/runner/work/mlf-core/exploding_springfield" not found

What am I doing wrong?

Thank you very much!
Cheers

[lewislbr]

Adding to this, the path doesn't seem to be passed to dockerfile, having to rewrite the path (in this case folder1) like:

- name: Build and push Docker images
        uses: docker/build-push-action@master
        with:
          path: folder1
          dockerfile: folder1/Dockerfile
          username: ${{ secrets.DOCKER_USERNAME }}
          password: ${{ secrets.DOCKER_PASSWORD }}
          repository: lewislbr/random

to make it work.

[crazy-max]

@Zethson This will be solved through build-push-action v2 (#92) as it's written as a typescript-action to be as closed as possible of the GitHub Runner during its execution. You can already try it with:

• https://github.com/docker/setup-buildx-action
• https://github.com/docker/setup-qemu-action
• https://github.com/docker/login-action

[crazy-max]

Version 2 has been merged to the main branch and is therefore available via uses: docker/build-push-action@v2 (mutable tag).

As a reminder, this new version changes drastically and works with 3 new actions (login, setup-buildx and setup-qemu) that we have created. Many usage examples have been added to handle most use cases.

And it should fix this current issue. Don't hesitate if you have any questions.

[Zethson]

Thanks. I will try it out and report back if I run into issues. Thursday, 10 September 2020, 00:46AM +02:00 from CrazyMax notifications@github.com :

…

Version 2 has been merged to the main branch and is therefore available via uses: ***@***.*** (mutable tag). As a reminder, this new version changes drastically and works with 3 new actions ( login , setup-buildx and setup-qemu ) that we have created. Many usage examples have been added to handle most use cases. And it should fix this current issue. Don't hesitate if you have any questions. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub , or unsubscribe .