accessing a container from the cli?

[nktech1135]

Hi all.
I was wondering how one would go about accessing a container via the cli if logged in via ssh?
Is there a cubernetes command for this? or some other method?

Thanks.

 

[sretalla]

Using SCALE Apps |

Using SCALE Apps

www.truenas.com

Accessing the Shell in an Active Container
To access the shell in an active container, first identify the namespace and pod for the container. In the Scale UI, go to System Settings > Shell to begin entering commands:

1. View container namespaces: k3s kubectl get namespaces.
2. View pods by namespace: k3s kubectl get -n <NAMESPACE> pods.
3. Access container shell: k3s kubectl exec -n <NAMESPACE> --stdin --tty <POD> -- /bin/bash.

 

[nktech1135]

Thanks. that's what i needed. I'm running these commands via ssh because the shell in the UI doesn't work with screen readers. Plus, i generally prefer ssh anyway.

 

[Heavy]

Sorry for re-opening this but I updated heavyscript to handle the process of finding your container(s) and opening a shell, as explained by @sretalla I thought it would come in handy for those who are not well versed in kubernetes..

Source code:

GitHub - Heavybullets8/heavy_script: Bash script for managing Truenas SCALE applications, automatically update applications, backup applications datasets, open a shell for containers.

Bash script for managing Truenas SCALE applications, automatically update applications, backup applications datasets, open a shell for containers. - GitHub - Heavybullets8/heavy_script: Bash script...

github.com

Instructions

1. Type in

Code:

bash heavy_script.sh

2. Select Option 9

3. Type the number that corresponds with the application you want to shell into

4. If there are multiple containers for that application, it will open another menu to select which one you want, otherwise it will default to the only container available

5. Choose either option 1 or 2

And that is it, if there is a shell available, it will try /bin/bash first, then fallback to /bin/sh if bash is not available.
Afterwards, type exit, to exit the shell.

 

[alugowski]

I wrote a quick script based on strella's link that works for single-container pods:

Code:

#!/usr/bin/env bash

# Get the container namespace.
# This command lists all namespaces:
# k3s kubectl get namespaces
# TrueNAS namespaces for Docker containers are just the container name prefixed with 'ix-'
NAMESPACE="ix-$1"
shift

# view pods in namespace:
# k3s kubectl get -n <NAMESPACE> pods
# returns a header line then the container pod is in the first column of the next line. Assume there is only one pod.
POD="$(k3s kubectl get -n $NAMESPACE pods | tail -n 1 | awk '{print $1}')"

# Run a shell in the container:
if [[ $# -eq 0 ]]; then
    COMMAND="/bin/sh"
    k3s kubectl exec -n $NAMESPACE --stdin --tty $POD -- $COMMAND
else
    # Forward remaining parameters to the command
    k3s kubectl exec -n $NAMESPACE --stdin --tty $POD -- $@
fi

For a shell (/bin/sh):

Code:

sudo ./container-shell.sh <appname>

or any arbitrary command, including a different shell:

Code:

sudo ./container-shell.sh <appname> cmd arg1 arg2 arg3 etc

 

[Aviatorpaal]

How do I run a command as a specific user inside a K3S Kubernetes container (all the layers )? These two commands are doing exactly what I want to be done when run individually, in sequence:

Code:

k3s kubectl exec -n ix-nextcloud -i -t nextcloud-6956776979-grgvw -c nextcloud -- /bin/bash
su -s /bin/bash -c "./occ files:scan --all" www-data

However, I would like to automate this, and therefore need to combine them into one script for TrueNAS Scale to run

 

[Arwen]

Short answer: HereIS

Longer answer, script with this:

Code:

#!/bin/bash
k3s kubectl exec -n ix-nextcloud -i -t nextcloud-6956776979-grgvw -c nextcloud -- /bin/bash <<HereIS
su -s /bin/bash -c "./occ files:scan --all" www-data
new command...
next command...
exit
HereIS
exit

The word "HereIS" can be anything unique. It is basically a wrapper for standard input to the following commands.

The first "exit" is exiting out of the container, and the second is exiting the SCALE bash script.

It's been a while since I've coded something like this... so test with something harmless at first.

 

[Aviatorpaal]

Short answer: HereIS

Longer answer, script with this:

Code:

#!/bin/bash
k3s kubectl exec -n ix-nextcloud -i -t nextcloud-6956776979-grgvw -c nextcloud -- /bin/bash <<HereIS
su -s /bin/bash -c "./occ files:scan --all" www-data
new command...
next command...
exit
HereIS
exit

The word "HereIS" can be anything unique. It is basically a wrapper for standard input to the following commands.

The first "exit" is exiting out of the container, and the second is exiting the SCALE bash script.

It's been a while since I've coded something like this... so test with something harmless at first.

Awesome - thanks for your time, much appreciated.

It appears to be working, but the following warning/error is thrown:
Unable to use a TTY - input is not a terminal or the right kind of file

Edit: rookie mistake - I was requesting an interactive TTY. Removed the "-t" and it now works as intended. Awesome!

 

[Arwen]

Awesome - thanks for your time, much appreciated.

It appears to be working, but the following warning/error is thrown:
Unable to use a TTY - input is not a terminal or the right kind of file

Edit: rookie mistake - I was requesting an interactive TTY. Removed the "-t" and it now works as intended. Awesome!

Glad I was able to help.

Unix is extremely flexible and has a lot of odd things embedded in it.