truecharts / public

Community Helm Chart Repository
https://truecharts.org
GNU Affero General Public License v3.0
1.16k stars 616 forks source link

Vlmcsd does not have pod port mapped to host port #16908

Closed vianchiel closed 10 months ago

vianchiel commented 11 months ago

App Name

vlmcsd-kms-server

Operating System

TrueNAS SCALE 23.10.1

App Version

4.1.5

Application Events

No events are available.

Application Logs

2024-01-06 20:39:00.653493+08:002024-01-06 12:39:00: Read KMS data file version 2.0 //vlmcsd.kmd
2024-01-06 20:39:00.653552+08:002024-01-06 12:39:00: Listening on [::]:1688
2024-01-06 20:39:00.653564+08:002024-01-06 12:39:00: Listening on 0.0.0.0:1688
2024-01-06 20:39:00.653582+08:002024-01-06 12:39:00: Using CSVLK Windows (Windows Server 2019) with random ePID 05426-00206-562-960115-03-1074-9200.0000-2552019
2024-01-06 20:39:00.653605+08:002024-01-06 12:39:00: Using CSVLK Office2010 (Office 2010) with random ePID 05426-00096-200-166274-03-1074-9200.0000-2522014
2024-01-06 20:39:00.653620+08:002024-01-06 12:39:00: Using CSVLK Office2013 (Office 2013) with random ePID 05426-00206-245-419375-03-1074-9200.0000-1982018
2024-01-06 20:39:00.653630+08:002024-01-06 12:39:00: Using CSVLK Office2016 (Office 2016) with random ePID 05426-00206-453-681268-03-1074-9200.0000-2822023
2024-01-06 20:39:00.653637+08:002024-01-06 12:39:00: Using CSVLK WinChinaGov (Windows 10 China Government) with random ePID 05426-03858-277-872931-03-1074-9200.0000-2462019
2024-01-06 20:39:00.653649+08:002024-01-06 12:39:00: Using CSVLK Office2019 (Office 2019) with random ePID 05426-00206-674-015059-03-1074-9200.0000-2862018
2024-01-06 20:39:00.653656+08:002024-01-06 12:39:00: vlmcsd svn1113-3-g65228e5, built 2022-08-11 06:38:46 UTC started

Application Configuration

image image image image

Describe the bug

The application in the pod does not have a host port mapped to 1688. This results in failure to contact the kms server inside the pod.

Following results using k3s kubectl describe pod

Controlled By:  ReplicaSet/vlmcsd-vlmcsd-kms-server-7c8c6f9b48
Containers:
  vlmcsd-vlmcsd-kms-server:
    Container ID:   containerd://6bdc1e3259e6ee76da187a36a39ec7ceeabde9200513d03095df726ef64a062b
    Image:          mikolatero/vlmcsd:latest@sha256:217a03280410aa06bca7dd1b4e3e206317ba740a990d90683462fb21b17c9e7d
    Image ID:       docker.io/mikolatero/vlmcsd@sha256:217a03280410aa06bca7dd1b4e3e206317ba740a990d90683462fb21b17c9e7d
    Port:           <none>
    Host Port:      <none>
    State:          Running
      Started:      Sat, 06 Jan 2024 20:39:00 +0800
    Ready:          True

To Reproduce

  1. Install the app using the default parameters same as my configuration
  2. Wait for application to deploy
  3. Enter shell in truenas scale and use root
  4. Run # k3s kubectl get namespaces to get the app's namespace, likely ix-[appname]
  5. Run # k3s kubectl -n ix-[appname] get pods to get the pod's name
  6. Run # k3s kubectl -n ix-[appname] describe pod [podname] and get the running configuration

Expected Behavior

The application should automatically map host port 1688 to pod port 1688

Screenshots

NA

Additional Context

The chart should either automatically map port 1688 between pod and host OR The chart should allow customised port for the pod and host

I've read and agree with the following

vianchiel commented 10 months ago

Hi @Ornias1993 and @xstar97 , thanks for the following up the issue. I've tried the new version 4.1.6 by both upgrading and fresh installing the app. The issue still persists and ports are still not mapped between pod and host.

I tried: Activating a win11 hyper-v VM per instructions at https://github.com/mikolatero/docker-vlmcsd (No connection) and Using my above mentioned k3s kubectl describe pod (Ports are still None)

xstar97 commented 10 months ago

The catalog item doesn't have the updated code, so the rpc port isn't even exposed yet 🤦‍♂️

vianchiel commented 10 months ago

Thanks for the clarification, I'll wait patiently in this case.

truecharts-admin commented 1 month ago

This issue is locked to prevent necro-posting on closed issues. Please create a new issue or contact staff on discord of the problem persists