postCreateCommand doesn't run in the right context?

[cgestes]

What happened?

[16:37:48] debug Run post create commands...
[16:37:48] info Run command : ./bash/local/codespaces_init.sh...
[16:37:48] debug Executing command : [su codespace -c ./bash/local/codespaces_init.sh]...
[16:37:48] error ./bash/local/codespaces_init.sh: line 3: pyenv: command not found

pyenv is installed in our Dockerfile, it is working in codespace.

What did you expect to happen instead?
pyenv should be found.

.devcontainer:

{
	"build": {
		"dockerfile": "../Dockerfile"
	},
	"postCreateCommand": "./bash/local/codespaces_init.sh"
}

Local Environment:

• DevPod Version: 0.5.7
• Operating System: mac
• ARCH of the OS: ARM64

DevPod Provider:

• Local/remote provider: docker

[samsaket7]

Hi @cgestes,

I’m encountering a similar issue. Were you able to find a resolution?

Edit: In my case, it appears that the ENV variable for PATH set in the Dockerfile didn’t take effect. Exporting the PATH in the post-create script resolved the problem for me.

[pascalbreuninger]

Hi @cgestes @samsaket7, this should also be fixed with #1184 and available with the next release

[eguiraud]

Hi, this is still broken in the latest version for me: #1234