Remove *_ROOT_PARENT env variables

[cgardens]

Tell us about the problem you're trying to solve

We do not want developers to need to create all of the directory structure needed for airbyte to run. In order to do that we have hacked on HACK_WORKSPACE_ROOT_PARENT and HACK_LOCAL_ROOT_PARENT. The env variables must be parents of whatever WORKSPACE_ROOT and LOCAL_ROOT AND they must already exist on the local filesystem. This gives our docker compose a handle to create the needed directories that we want to use as mounts for our other services.

Describe the solution you’d like

This is obviously a pretty ugly hack and we would like to remove the need for env variables.

┆Issue is synchronized with this Asana task by Unito

[Amanraj0007]

Hi @cgardens
I am exploring docker deployment of airbyte and i encountered a service init which is creating /tmp/airbyte_local

which is getting mounted on server and worker's container.

what is significance of this directory. why do we need this ?

is it necessary to be created on host only where docker deamon is running? or we could create and mount from any filesystem services.

[cgardens]

no longer relevant with the upcoming deprecation of docker compose.