Add ability to opt out of agent auto-update

Describe the enhancement

Running the agent within docker and having it auto update causes the container to throttle and never succeed without having to manage PID 1

It would be nice to have something in config.sh or run.sh, possibly environment variables to help opt out of auto-update

Code Snippet

n/a

Additional information

n/a

[bryanmacfarlane]

Also note in the short term if you are running the runner in a container, you should call the ./runsvc.sh entrypoint and not ./run.sh which is meant for interactive running. Calling ./runsvc.sh will at least handle the update and not exit.

In the medium term, we also want to support .container in the yaml when running in K8s so at least the container your job runs in (the steps) can stay static and is decoupled from the runner. That also means you don’t have to build the runner into your containers. That’s how it works with VM self-hosted - the runner on the host execs steps in the container you bring.

Finally, we should consider refactoring as @ioquatix referred to into the base runner (listener) and the steps portion which is derived from the service yaml orchestration.

[ioquatix]

Here is my suggestions:

• Don’t want self-updating features, it’s deployed as a versioned package. If an update is needed we will release a new package.
• Please separate the files according to unix conventions: read-only area for binaries/assets and a directory for runtime state, e.g. the user’s home directory, or allow it to be specified on the command line.