Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description

When building from an empty directory, podman remote logs an unexpected "EOF" error.

Steps to reproduce the issue:

(Tested using the quay.io/podman/upstream image)

1. Setup an empty build context and an Dockerfile not located in this build context:

[root@fa7e0c9e34d1 /]# mkdir empty-directory
[root@fa7e0c9e34d1 /]# echo "FROM scratch" > Dockerfile

2. Try to build this image with an empty build context without using remote podman, it works:

[root@fa7e0c9e34d1 /]# podman build -f Dockerfile empty-directory/
STEP 1/1: FROM scratch
COMMIT
--> 8540bc5d966
8540bc5d966cc291b91b724dcd49b51674d12a30cd1375fdfa7e9fb048723217

3. Start a podman server, and try the same thing with podman remote, it seems to work, but it logs an unexpected EOF error:

[root@fa7e0c9e34d1 /]# podman system service -t 0 &
[1] 56
[root@fa7e0c9e34d1 /]# podman --remote build -f Dockerfile empty-directory/
ERRO[0000] While reading directory /empty-directory: EOF
STEP 1/1: FROM scratch
COMMIT
--> 13f8e206674
13f8e20667465573de921f6e98356d4d6acb7d923739e554ad232fffa80888d0

Describe the results you received:
There is an unexpected log ERRO[0000] While reading directory /empty-directory: EOF when using podman remote.

Describe the results you expected:
There should be no error log.

Additional information you deem important (e.g. issue happens only occasionally):

Output of podman version:

[root@fa7e0c9e34d1 /]# podman version
Client:       Podman Engine
Version:      4.3.0-dev
API Version:  4.3.0-dev
Go Version:   go1.18.6
Built:        Thu Jan  1 00:00:00 1970
OS/Arch:      linux/amd64