Ensure exec command can find config.json

[Furisto]

Partially fixes #584. While fixing this I discovered another issue, which I will follow up in the next PR.

[utam0k]

@Furisto I'm sorry, but could you rebase?

[codecov-commenter]

Codecov Report

Merging #616 (31c30af) into main (63f77b2) will decrease coverage by 0.01%.
The diff coverage is 0.00%.

@@            Coverage Diff             @@
##             main     #616      +/-   ##
==========================================
- Coverage   70.01%   69.99%   -0.02%     
==========================================
  Files          82       82              
  Lines       10933    10936       +3     
==========================================
  Hits         7655     7655              
- Misses       3278     3281       +3     

[Furisto]

@utam0k PTAL

[utam0k]

@Furisto Thanks for your PR 😍
Doesn't this break the exec command? The config.json should not be in the bundle directory. I tried the following command and it failed.

$ sudo podman run --name test -it busybox sh
/ 
# and in another console
$ sudo podman exec -it test sh

[Furisto]

@utam0k The exec command is already broken. This fixes one of the issues (missing config.json), but there is another issue which I alluded to the in the description of this issue which breaks the exec command later on.

The config.json should not be in the bundle directory.

Unless I am misunderstanding your meaning, it is in the bundle directory.

[utam0k]

@utam0k The exec command is already broken. This fixes one of the issues (missing config.json), but there is another issue which I alluded to the in the description of this issue which breaks the exec command later on.

The config.json should not be in the bundle directory.

Unless I am misunderstanding your meaning, it is in the bundle directory.

Oh, my local was wrong.

[utam0k]

LGTM