You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In the container image docker.io/ovhcom/venom:v1.2.0 the path of Venom binary is /usr/local/venom.
The directory /usr/local is not in the PATH (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin).
This means that I need to look up (because I am forgetful) and use the full path to the binary if I want to run commands inside a Venom container that is already running (eg. docker run --entrypoint sh -it docker.io/ovhcom/venom:v1.2.0). I am also using the Venom image in GitLab CI and have to use the full path there, too, because the GitLab Runner starts the container with a shell and uses the shell to run Venom.
Although this is only a little inconvenience it would be nice if the binary could be placed at /usr/local/bin/venom instead so that I do not need to use the full path anymore.
In the container image
docker.io/ovhcom/venom:v1.2.0
the path of Venom binary is/usr/local/venom
.The directory
/usr/local
is not in the PATH (/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin
).This means that I need to look up (because I am forgetful) and use the full path to the binary if I want to run commands inside a Venom container that is already running (eg.
docker run --entrypoint sh -it docker.io/ovhcom/venom:v1.2.0
). I am also using the Venom image in GitLab CI and have to use the full path there, too, because the GitLab Runner starts the container with a shell and uses the shell to run Venom.Although this is only a little inconvenience it would be nice if the binary could be placed at
/usr/local/bin/venom
instead so that I do not need to use the full path anymore.venom/Dockerfile
Line 6 in 5e480f0
The text was updated successfully, but these errors were encountered: