JKube should not pick the Dockerfile where the podman daemon is executed

[sunix]

Describe the bug

In Dockerfile mode with podman, if podman daemon is executed in a directory that is not the project folder and that contains a Dockerfile, the build task/goal is picking the Dockerfile in the podman daemon directory and not the project one.

Eclipse JKube version

SNAPSHOT

Component

JKube Kit

Apache Maven version

3.6.3

Gradle version

No response

Steps to reproduce

1. Create/Clone a project with a Dockerfile in the root directory of the project
2. Create another Dockerfile in your home directory
3. Start the podman daemon in your home directory, and keep it running

   cd /home/sunix && podman system service --time=0 unix:/run/user/$(id -u)/podman.sock
   

4. in another terminal, tell jkube to use podman by referencing the podman.sock file

   export DOCKER_HOST="unix:/run/user/$(id -u)/podman.sock"
   

5. go to the project folder and run the build task or goal

   mvn package k8s:build
   

I managed to figure out it wasn't picking the right Dockerfile in debug mode:

Expected behavior

Dockermode should pick the Dockerfile located in the project.

Runtime

Kubernetes (vanilla)

Kubernetes API Server version

other (please specify in additional context)

Environment

Linux

Eclipse JKube Logs

No response

Sample Reproducer Project

No response

Additional context

No response

[sunix]

probably related to containers/podman#13293 (comment)

[manusa]

probably related to containers/podman#13293 (comment)

Yes, from your description and internal discussion, this seems more like a Podman related issue. Since we're sending the container build configuration and files through the Docker-compatible REST API.

[sunix]

TODO @sunix try with newer version of podman
Current version: podman version 3.2.3

[sunix]

I just upgraded podman to version 4.3.1 and I cannot reproduce anymore. Closing this issue.