[Request]: Consistent `container` executable path in integration tests

[katiewasnothere]

Feature or enhancement request details

Today, when we run our integration tests via make integration, the make command will start the container binary from ./bin (see here). Later the integration tests may run some CLI commands to container and when they do, they look for the executable path to container at ./.build (see here).

This behavior has not caused any issues today since the container binary in ./bin and ./.build will be the same per the makefile. However, this becomes an issue if a CLI test wants to restart container (for example, as a test for #1600 would need to do). In this case, the integration tests would attempt to start container from ./.build, which would then fail to find the required plugins for container to start successfully.

The logs would look like this:

initializing plugin loader [installRoot=/apple/container/.build/]
detecting user plugins directory [path=/apple/container/.build/libexec/container-plugins]
discovered plugin directory [path=/apple/container/.build/libexec/container/plugins]
helper failed [name=container-apiserver] [error=internalError: "cannot find any plugins with type network"]

We should be using a consistent path for container in our integration tests.

Code of Conduct

• I agree to follow this project's Code of Conduct