search

vsys-host / shkeeper.io

SHKeeper is a self-hosted and open-source cryptocurrency gateway payment processor. It's integrate with popular CMS, any e-commerce, your own code or product
https://shkeeper.io/
GNU General Public License v3.0
286 stars 74 forks source link

Unable to Set Up Shkeeper: Pods Stuck in CreateContainerConfigError #75

Open NIKIB0Y opened 6 days ago

NIKIB0Y commented 6 days ago

I am unable to successfully set up Shkeeper on my server despite multiple attempts. The installation process completes without errors, but several pods remain in a CreateContainerConfigError state.

Server Details:

Specs:
    48 CPU cores
    1 TB disk space (50% free, no system overload)

Steps to Reproduce:

Execute the following reinstall script:

helm uninstall shkeeper
helm uninstall my-shkeeper
helm uninstall kubernetes-secret-generator
helm repo remove vsys-host
helm repo remove mittwald
/usr/local/bin/k3s-uninstall.sh
rm /root/.kube/config
rm /root/.kube
kubectl get all --all-namespaces  # to verify if everything is uninstalled
curl -sfL https://get.k3s.io | sh -
mkdir /root/.kube && ln -s /etc/rancher/k3s/k3s.yaml /root/.kube/config
ln -s /etc/rancher/k3s/k3s.yaml /root/.kube/config
curl https://raw.githubusercontent.com/helm/helm/main/scripts/get-helm-3 | bash
helm repo add vsys-host https://vsys-host.github.io/helm-charts
helm install -f /root/shkeeper/values.yaml shkeeper vsys-host/shkeeper

Use the following values.yaml configuration:


    storageClassName: local-path

    btc:
      enabled: true
    ltc:
      enabled: true
    doge:
      enabled: true

    monero:
      enabled: true
      fullnode:
        enabled: true
Run kubectl get pods -n shkeeper.

Observed Behavior: The following pods remain in a CreateContainerConfigError state:

NAME                                    READY   STATUS                       RESTARTS   AGE
bitcoind-deployment-6b546df5df-vsdk8    0/2     CreateContainerConfigError   0          2m59s
dogecoind-deployment-56848bf96c-f5k66   0/2     CreateContainerConfigError   0          2m59s
litecoind-deployment-694bf4f69c-sp7j8   0/2     CreateContainerConfigError   0          2m59s
mariadb-9fdf5b-jn6sv                    1/1     Running                      0          2m59s
monero-wallet-rpc-59fdb654b9-bnlwc      0/1     CreateContainerConfigError   0          2m59s
monerod-d446c4c7c-2mkvh                 1/1     Running                      0          2m59s
shkeeper-deployment-86f685b469-sq46t    0/1     CreateContainerConfigError   0          2m59s

Expected Behavior: All pods should be up and running successfully.

Additional Information:

I’ve tried using both the default and modified values.yaml files, but the result is the same. The server has enough resources, so this is unlikely to be a resource issue.

I need help to identify the root cause of this issue. Let me know if additional logs or debugging information is required.

Thank you!

yukonet commented 3 days ago

There are missing lines in provided reinstall script:

helm repo add mittwald https://helm.mittwald.de
helm repo update
helm install kubernetes-secret-generator mittwald/kubernetes-secret

Did you run these commands? Check if the kubernetes-secret-generator pod was created with the command:

kubectl get pods