Why is ZEPHYR_BASE hard coded?

[NINI1988]

In https://github.com/zephyrproject-rtos/docker-image/blob/fe38bd9eef84fa1596c35e485ef8fbd2a509bc54/Dockerfile.devel#L37 ZEPHYR_BASE is hard coded and prevents the usage of my .west/config file:

[zephyr]
base = deps/zephyr

Without the hard coded ZEPHYR_BASE, west will automatically find zephyr.base from the config file and does't require this. Is there a reason for that? I have zephyr under folder deps, so the hard code path does not exists.

I would like to extend the already build image from ghcr.io/zephyrproject-rtos/zephyr-build:v0.26.4 and extend that for my usage. But it is not possible in docker to unset an env variable (https://stackoverflow.com/questions/55789409/how-to-unset-env-in-dockerfile). Otherwise I have to call unset ZEPHYR_BASE before every command.

[stephanosio]

It mostly has to do with the (quite outdated and far from ideal) instructions given in the README.

I am not against the idea of removing ENV ZEPHYR_BASE since not doing so reduces the reusability of the image -- we just need to update the instructions in the README accordingly.

[bayrem-gharsellaoui]

Did you find a way around that?

[abenezerarg]

status?