Using remoteUser means env vars aren’t set

[ladlestein]

I’ve been using shell-history just find with VSCode on Linux. Now I’ve added a remoteUser property to the .devcontainer.json file, and I’m getting that error message at the beginning of the shell-history install.sh script.

Ok, fair enough, but do you know why explicitly setting the remoteUser property causes the _REMOTE_USER and _REMOTE_USER_HOME env variables to not be set?

[stuartleeks]

I believe that this should be addressed with #16 and the subsequent changes that are released in 0.0.5 of shell-history as _REMOTE_USER_HOME isn't used any more :-)

[jwaldrip]

This looks to still being an issue when using coders envbuilder

#1: Running: [/bin/sh -c _CONTAINER_USER="root" _REMOTE_USER="vscode" ./install.sh]
Activating feature 'shell-history'
User: vscode     User home:
***********************************************************************************
*** Require _REMOTE_USER and _REMOTE_USER_HOME to be set (by dev container CLI) ***
***********************************************************************************
Failed to build: do build: error building stage: failed to execute command: waiting for process to exit: exit status 1
Falling back to the default image...
error: do build: error building stage: failed to execute command: waiting for process to exit: exit status 1: no fallback image has been specified
error: running command "envbuilder": do build: error building stage: failed to execute command: waiting for process to exit: exit status 1:
    github.com/coder/envbuilder.run.func4
        /home/runner/work/envbuilder/envbuilder/envbuilder.go:271
  - no fallback image has been specified%