Launching container as UID 1000 prompts for zsh configuration

[jeffcpullen]

While testing the latest release of the the dev container I found that the terminal is captured in the zsh configuration TUI.

% podman run --rm -it -u 1000 ghcr.io/ansible/community-ansible-dev-tools:v24.12.0

This is the Z Shell configuration function for new users,
zsh-newuser-install.
You are seeing this message because you have no zsh startup files
(the files .zshenv, .zprofile, .zshrc, .zlogin in the directory
~).  This function can help you with a few settings that should
make your use of the shell easier.

You can:

(q)  Quit and do nothing.  The function will be run again next time.

(0)  Exit, creating the file ~/.zshrc containing just a comment.
     That will prevent this function being run again.

(1)  Continue to the main menu.

--- Type one of the keys in parentheses --- 

An inspection of the image shows that the 'CMD' parameter is set to the following.

"Cmd": [
                    "zsh"
               ],

If zsh is required it would seem that a default configuration file should be created to prevent the terminal from being captured in the setup screen.

Out of curiousity, is zsh actually required? I switch between it and bash frequently due to OS defaults and have never really noticed a difference. Rather than trying to solve the zsh configuration screen, perhaps switching CMD to /bin/bash would make more sense as it is the Fedora base image default.

% podman run --rm -it -u 1000 ghcr.io/ansible/community-ansible-dev-tools:v24.12.0 /bin/bash
bash-5.2$

[syaghoubi00]

It seems like when a user is logged in and not in /etc/passwd the $HOME dir is being set to /runner/.

I noticed there was also a directory of /home/runner/, which is empty.

The name runner makes me think that it is some artifact of the workflow building the container.

[1000@bfde08b45743]~% ls $HOME
artifacts  env  inventory  project

The artifacts directory seems to backup the idea that its something leftover from workflow.

Since there is no .zshrc in the $HOME dir, the zsh-newuser-install gets triggered.

A possible fix may be to add zsh-newuser-install() { :; } to /etc/zshenv during the container build.

[jeffcpullen]

This is still an issue with version v25.5.1