Open echo-devnull opened 1 year ago
Does the pod have any notable logs? It sounds like the SSH server inside of the pod never became happy, for whatever reason.
No all the logging is in the original post I'm afraid. The pod itself did not create any logging.
That's... bizarre. Makes me think something went wrong with the image being downloaded. Can you try again but ensure that your nodes don't have an existing linuxserver/openssh-server
image present? That should download the latest image and hopefully work 😓
I've got the time to look into this again ;-)
So, the expose (reverse tunnel) pod that get's created does have a single log entry:
[mod-init] Attempting to run Docker Modification Logic
But does not move beyond that, or ever get to the ready status.
According to describe
the pod itself is running, but the Readiness probe failed. It is trying to connect to "2222" ? That seems wrong to me. Should it not be "22" ?
Nevermind, it seems to indeed be the default number: https://docs.linuxserver.io/images/docker-openssh-server
@echo-devnull Is there some sort of firewall being used? I believe that part of the linuxserver openssh image downloads a git repo at runtime, so I wonder if it's something related to that? Or, DNS lookup issues. Spitballing ideas. I haven't been able to repro this so I don't know what else to suggest 😭
I created a kubernetes service that listens on port 222 which I want to "reverse tunnel" to my local machine.
Then I expose it via:
But the pod that gets created, never actually gets to "running" state:
The yaml:
And the logging from the running localizer: