Running the `ps ax` command from kurtosis shell truncates lines to 80 characters

[winksaville]

What's your CLI version?

0.88.16

Description & steps to reproduce

I was running the example ethereum-package setup from reth private-testnet .

I then ran:

wink@fwlaptop 24-04-16T20:37:33.589Z:~/kurtosis-pn1-reth-lighthouse
$ kt service shell dazzling-geyser el-1-reth-lighthouse 
Found bash on container; creating bash shell...
root@a51f74e560d0:/# ps ax
    PID TTY      STAT   TIME COMMAND
      1 ?        Ss     0:00 /sbin/docker-init -- sh -c reth init --datadir=/dat
      7 ?        S      0:00 sh -c reth init --datadir=/data/reth/execution-data
     15 ?        Sl     6:12 reth node -vvv --datadir=/data/reth/execution-data 
    878 pts/0    Ss     0:00 sh -c if command -v 'bash' > /dev/null; then ..echo
    884 pts/0    S      0:00 bash
    887 pts/0    R+     0:00 ps ax
root@a51f74e560d0:/# 

And you can see the output of the ps ax command is truncated to 80 characters.

Desired behavior

The output should not be truncated, a work-around was to redirect the output to cat then I can see all of the output:

root@a51f74e560d0:/# ps ax | cat
    PID TTY      STAT   TIME COMMAND
      1 ?        Ss     0:00 /sbin/docker-init -- sh -c reth init --datadir=/data/reth/execution-data --chain=/network-configs/network-configs/genesis.json && reth node -vvv --datadir=/data/reth/execution-data --chain=/network-configs/network-configs/genesis.json --http --http.port=8545 --http.addr=0.0.0.0 --http.corsdomain=* --http.api=admin,net,eth,web3,debug,trace --ws --ws.addr=0.0.0.0 --ws.port=8546 --ws.api=net,eth --ws.origins=* --nat=extip:172.16.4.11 --authrpc.port=8551 --authrpc.jwtsecret=/jwt/jwtsecret --authrpc.addr=0.0.0.0 --metrics=0.0.0.0:9001
      7 ?        S      0:00 sh -c reth init --datadir=/data/reth/execution-data --chain=/network-configs/network-configs/genesis.json && reth node -vvv --datadir=/data/reth/execution-data --chain=/network-configs/network-configs/genesis.json --http --http.port=8545 --http.addr=0.0.0.0 --http.corsdomain=* --http.api=admin,net,eth,web3,debug,trace --ws --ws.addr=0.0.0.0 --ws.port=8546 --ws.api=net,eth --ws.origins=* --nat=extip:172.16.4.11 --authrpc.port=8551 --authrpc.jwtsecret=/jwt/jwtsecret --authrpc.addr=0.0.0.0 --metrics=0.0.0.0:9001
     15 ?        Sl     6:16 reth node -vvv --datadir=/data/reth/execution-data --chain=/network-configs/network-configs/genesis.json --http --http.port=8545 --http.addr=0.0.0.0 --http.corsdomain=* --http.api=admin,net,eth,web3,debug,trace --ws --ws.addr=0.0.0.0 --ws.port=8546 --ws.api=net,eth --ws.origins=* --nat=extip:172.16.4.11 --authrpc.port=8551 --authrpc.jwtsecret=/jwt/jwtsecret --authrpc.addr=0.0.0.0 --metrics=0.0.0.0:9001
    878 pts/0    Ss     0:00 sh -c if command -v 'bash' > /dev/null; then ..echo "Found bash on container; creating bash shell..."; bash;         else  ..echo "No bash found on container; dropping down to sh shell..."; sh;  .fi
    884 pts/0    S      0:00 bash
    924 pts/0    R+     0:00 ps ax
    925 pts/0    S+     0:00 cat
root@a51f74e560d0:/# 

What is the severity of this bug?

Papercut; this bug is frustrating, but I have a workaround.

What area of the product does this pertain to?

CLI: the Command Line Interface

[tedim52]

Thanks for filing this @winksaville !