How are containers started? Can they be started with a login shell?

[ndw]

Apologies if this is a misplaced question. I have a custom container that I use for a build. if I test it by running

docker run -it --rm --volume builder-home:/home/builder custom-build /bin/bash

I see what I expect and everything works, because /bin/bash has run a login shell for me.

But when I use the container in a Woodpecker job, I get an environment with the correct UID and the right home directory mounted and such, but ~/.bashrc hasn't been run. I guess it isn't a login shell. Consequently, there are parts of the configuration missing.

I can "fix" this by running

/bin/bash -l -c "command and arguments"

in the job, but that's kind of tedious. Is there a way to get the environment to be correct? Or, if I'm doing this all wrong, what should I be doing instead?

The most significant part of the custom environment that requires a login shell is pyenv. I want to install some custom Python modules that aren't bundled in Debian. Attempting to mix pip install with the global Python install doesn't work anymore.

[qwerty287]

Is there a difference to #5853?

[ndw]

Goodness me, I am a moron. "No." Apologies.