Weird Gitlab-Runner output

Dear Clear Linux Team,

I am trying to use clearlinux together with gitlab(-runner) to set up my own CI. I could install everything perfectly as following this https://docs.gitlab.com/runner/install/linux-manually.html

It works now, however I have the problem that the corresponding runner always has in its log the following lines:

stty: 'standard input': Inappropriate ioctl for device
stty: 'standard input': Inappropriate ioctl for device
setterm: stdin does not refer to a terminal
stty: 'standard input': Inappropriate ioctl for device
stty: 'standard input': Inappropriate ioctl for device
stty: 'standard input': Inappropriate ioctl for device

Is there a way to configure this properly? I have no idea what is going on and I think supporting gitlab-runner would be a nice feature.

I did run clearlinux from a virtual machine that was hosted via VirtualBox. Maybe that could be one reason for the error?

Best,
Alessandro

You can open an package request issue on GitHub.

Note that this shouldn’t cause issues with the service itself. What bundles do you have installed on the system?

I wonder if this is related to some profile changes @mhorn made for the installer…

This is likely from the default profile run for the shell
/usr/share/defaults/etc/profile

19	# Ensure the interactive terminal has rows and columns
20	if [ -n "$PS1" ]; then # Only for interactive shells
21	  tty_rows=$(stty size | cut -d' ' -f1)
22	  tty_columns=$(stty size | cut -d' ' -f2)
23	  if [ $((${tty_rows} + 0)) -le 0 -o $((${tty_columns} + 0)) -le 0 ]; then
24	    [ -x /usr/bin/setterm ] &&  setterm --resize
25	    # fail safe if size still not set
26	    tty_rows=$(stty size | cut -d' ' -f1)
27	    tty_columns=$(stty size | cut -d' ' -f2)
28	    if [ $((${tty_rows} + 0)) -le 0 -o $((${tty_columns} + 0)) -le 0 ]; then
29	      stty rows 24 columns 80
30	    fi
31	  fi
32	  unset tty_rows tty_columns
33	fi

Somehow PS1 is being set cause the shell command to think you have a valid tty.

Hallo guys, I have bare metal installation of the latest version and have exact the same issue. What should be a possible solution for it?