Container starts with error message

[nsouedet]

Describe the bug
When I start my casa-dev env, the following error message occurs :
/.singularity.d/runscript: 91: /home/souedet/.bashrc: Bad substitution
The error is because dash is the default shell in our containers (/bin/sh is a link to /bin/dash).
So it forbids to add bash only compatible expressions like :
'[[ -z "" ]] && echo hello'

To Reproduce
Steps to reproduce the behavior:

1. Edit your ~/.bashrc
2. Append a bash compatible line but not dash compatible '[[ -z "" ]] && echo pouet'
3. Starts your container : bv bash
4. See error

Expected behavior
I think that ~/.bashrc should allow to contain compatible bash expressions when we start our casa-dev container.

Environment:

• Engine: Apptainer
• Version of BrainVISA: master branch
• Version of the casa-dev image: casa-dev-5.3-28

Additional context
To solve the issue we should reconfigure dash package to not be the default shell.
The following code should be added to casa-dev receipe:

echo "dash       dash/sh boolean false" | debconf-set-selections
DEBIAN_FRONTEND=noninteractive dpkg-reconfigure dash

[denisri]

That's strange, I don't get this.
If I append [[ -z "" ]] && echo pouet in the .bashrc of my environment home, I get this:

dr144257@is243176:~/casa_distro$ bv bash
pouet
(brainvisa-master-ubuntu-22.04)dr144257@is243176:/volatile/home/dr144257/casa_distro$ 

if I call sh or dash, I get:

dr144257@is243176:~/casa_distro$ bv sh
Apptainer> 

(no pouet).
Normally the .bashrc is only called when running a bash shell...
Or, I have an hypothesis:
do you have a .profile in your env home, which explicitly sources the .bashrc ? If so it's the reason: .profile is sourced by all sh shell variants, thus should not contain bash-specific or source bash-specific code. Otherwise you can use .bash_profile instead of .profile.

[nsouedet]

Many thanks Denis, I think you are true, my .profile explicitly sources my .bashrc.