Dear MOSIP Team,
We are currently evaluating MOSIP v1.2.0 using the official on-prem installation guide for internal testing.
While we have successfully set up the core services, Rancher, Keycloak, and other modules, we are blocked at the admin-service step. The referenced image (ghcr.io/mosip/admin-service:1.2.0) is not accessible publicly, and no GitHub authentication or alternate image instructions are provided in the documentation.
Could you kindly provide:
- Access to the Docker image for
admin-service
- Or the source code or
.jar with Dockerfile for sandbox use
We are using this strictly for testing in a private environment.
Thanks & Regards,
Ganeshkumar K
eMudhra Limited
Dear @Ganesh1305 ,
Welcome to the community and good to know that you are evaluating MOSIP, Let me look into this and ask one of our experts to help you with this.
Best Regards
Team MOSIP
Hello @Ganesh1305,
Thank you for reaching out.
You’re right — the image ghcr.io/mosip/admin-service:1.2.0 does not exist. In MOSIP, the correct image is: mosipid/admin-service:1.2.0.1
If you’re following the official on-prem installation guide, you don’t need to explicitly set the image . The install.sh script provided in the repo will handle the correct image and deploy the admin-service automatically.
To proceed:
- Make sure you’ve cloned the latest version of the mosip-infra repo
- Run the appropriate
install.sh script for your environment (e.g., admin-service or similar under the respective module path)
If you’re customizing values or running Helm commands manually, you can explicitly set the image as:
--set image.repository=<repo name>/<image name> --set image.tag=<tag>
Please try running the install.sh as per the documentation, and let us know if you run into any issues.
Thanks for evaluating MOSIP — happy to support your testing efforts!
Best Regards
Team MOSIP
Hi Praful,
Thanks for your support. We are facing similar issue will trying to install Kernel. Because admin-services and adminportal may have dependencies of kernel.
We have downloaded latest mosip-repo and when we executed .\install.sh we are getting the below error. Request your help.
root@deployment:~# kubectl get pods -n kernel
NAME READY STATUS RESTARTS AGE
auditmanager-6f69b4ff4b-c4q4x 1/2 CrashLoopBackOff 5 (23s ago) 4m9s
authmanager-765958bc7-gvtnd 1/2 CrashLoopBackOff 5 (26s ago) 4m11s
idgenerator-bc6b5dff7-ng94k 1/2 CrashLoopBackOff 4 (90s ago) 4m6s
masterdata-76cff79966-clxgk 1/2 CrashLoopBackOff 5 (6s ago) 4m2s
notifier-695f546586-g4xlj 1/2 CrashLoopBackOff 4 (48s ago) 3m37s
otpmanager-84cbddd669-bxs4h 1/2 CrashLoopBackOff 4 (75s ago) 3m57s
pridgenerator-9c4d64589-24j27 1/2 CrashLoopBackOff 4 (64s ago) 3m53s
ridgenerator-6f97654495-4sdz5 1/2 Error 5 (94s ago) 3m48s
syncdata-556ff6bf7b-cxd2b 1/2 CrashLoopBackOff 4 (81s ago) 3m42s
root@deployment:~# kubectl logs -n kernel -l app.kubernetes.io/name=auditmanager -c auditmanager --tail=100 -f
NOTE: Picked up JDK_JAVA_OPTIONS: -Xms1750M -Xmx1750M
Exception in thread “main” java.util.zip.ZipException: zip file is empty
at java.base/java.util.zip.ZipFile$Source.zerror(ZipFile.java:1607)
at java.base/java.util.zip.ZipFile$Source.findEND(ZipFile.java:1410)
at java.base/java.util.zip.ZipFile$Source.initCEN(ZipFile.java:1504)
at java.base/java.util.zip.ZipFile$Source.(ZipFile.java:1308)
at java.base/java.util.zip.ZipFile$Source.get(ZipFile.java:1271)
at java.base/java.util.zip.ZipFile$CleanableResource.(ZipFile.java:831)
at java.base/java.util.zip.ZipFile$CleanableResource$FinalizableResource.(ZipFile.java:857)
at java.base/java.util.zip.ZipFile$CleanableResource.get(ZipFile.java:846)
at java.base/java.util.zip.ZipFile.(ZipFile.java:248)
at java.base/java.util.zip.ZipFile.(ZipFile.java:177)
at java.base/java.util.jar.JarFile.(JarFile.java:350)
at java.base/java.util.jar.JarFile.(JarFile.java:321)
at java.base/java.util.jar.JarFile.(JarFile.java:287)
at org.springframework.boot.loader.jar.JarFile.(JarFile.java:115)
at org.springframework.boot.loader.jar.JarFile.(JarFile.java:109)
at org.springframework.boot.loader.jar.JarFile.(JarFile.java:95)
at org.springframework.boot.loader.jar.JarFile.(JarFile.java:86)
at org.springframework.boot.loader.archive.JarFileArchive.(JarFileArchive.java:60)
at org.springframework.boot.loader.archive.JarFileArchive.(JarFileArchive.java:56)
at org.springframework.boot.loader.archive.ExplodedArchive.getNestedArchive(ExplodedArchive.java:119)
at org.springframework.boot.loader.archive.ExplodedArchive.getNestedArchives(ExplodedArchive.java:106)
at org.springframework.boot.loader.PropertiesLauncher.getClassPathArchives(PropertiesLauncher.java:449)
at org.springframework.boot.loader.Launcher.launch(Launcher.java:49)
at org.springframework.boot.loader.PropertiesLauncher.main(PropertiesLauncher.java:593)
Events:
Type Reason Age From Message
Normal Scheduled 17m default-scheduler Successfully assigned kernel/auditmanager-6f69b4ff4b-c4q4x to 10.80.247.72
Normal Pulled 17m kubelet Container image “docker.io/istio/proxyv2:1.17.2” already present on machine
Normal Created 17m kubelet Created container istio-init
Normal Started 17m kubelet Started container istio-init
Normal Pulled 17m kubelet Container image “docker.io/istio/proxyv2:1.17.2” already present on machine
Normal Created 17m kubelet Created container istio-proxy
Normal Started 17m kubelet Started container istio-proxy
Normal Pulled 17m kubelet Successfully pulled image “docker.io/mosipid/kernel-auditmanager-service:1.2.0.1” in 2.53763903s
Normal Pulled 17m kubelet Successfully pulled image “docker.io/mosipid/kernel-auditmanager-service:1.2.0.1” in 4.716343207s
Normal Pulled 16m kubelet Successfully pulled image “docker.io/mosipid/kernel-auditmanager-service:1.2.0.1” in 3.989167489s
Normal Created 16m (x3 over 17m) kubelet Created container auditmanager
Normal Started 16m (x3 over 17m) kubelet Started container auditmanager
Normal Pulling 16m (x4 over 17m) kubelet Pulling image “docker.io/mosipid/kernel-auditmanager-service:1.2.0.1”
Warning BackOff 2m24s (x77 over 17m) kubelet Back-off restarting failed container
Regards,
Ganesh Kumar K
Hello @Ganesh1305,
Please go through the following checklist to ensure a smooth deployment:
- VM Resources
Have the created VMs been provisioned with the appropriate resources as specified in the MOSIP documentation?
Kindly verify CPU, memory, and disk allocations.
- External Services
Ensure all external services are up and running.
- Prerequisite Services Before Kernel Installation
Before installing the kernel, the following services must be running:
- Config Server Secrets
- Config Server
- Artifactory
- Key Manager
- WebSub
- Mock SMTP
- Masterdata Loader
- Installation Sequence
Please follow the correct sequence as outlined in the MOSIP deployment documentation.
Let us know if you encounter any issues or need further assistance.
Best Regards
Team MOSIP
Dear Praful,
Thanks for your support.
We have verified the VM Resources and with respect to external services we have installed the below services which initially required to make admin ui up.
External services
Dear Praful,
Thanks for your support.
We have verified the VM Resources and with respect to external services we have installed the below services which initially required to make admin ui up.
External services
- Postgres
- IAM (Keycloak)
- HSM
- Kafka
we have installed Config Server Secrets and below is the installation status
Create conf-secrets namespace Error from server (AlreadyExists): namespaces “conf-secrets” already exists Istio label namespace/conf-secrets not labeled Hang tight while we grab the latest from your chart repositories… …Successfully got an update from the “kafka-ui” chart repository …Successfully got an update from the “nfs-subdir-external-provisioner” chart repository …Successfully got an update from the “metallb” chart repository …Successfully got an update from the “codecentric” chart repository …Successfully got an update from the “ingress-nginx” chart repository …Successfully got an update from the “istio” chart repository …Successfully got an update from the “mosip” chart repository …Successfully got an update from the “prometheus-community” chart repository …Successfully got an update from the “rancher-latest” chart repository …Successfully got an update from the “stable” chart repository …Successfully got an update from the “bitnami” chart repository …Successfully got an update from the “jfrog” chart repository Update Complete. ⎈Happy Helming!⎈ Installing Secrets required by config-server NAME: conf-secrets LAST DEPLOYED: Thu May 22 14:35:14 2025 NAMESPACE: conf-secrets STATUS: deployed REVISION: 1 TEST SUITE: None
So, after this we are trying to install the Config Server but getting the error like CreateContainerConfigError.
We have tried with installing ./install.sh getting below error.
root@deployment:~/mosip-infra/deployment/v3/mosip/conf-secrets# kubectl logs -n config-server config-server-6947d4b546-xwnsh -c config-server --tail=100
Error from server (BadRequest): container “config-server” in pod “config-server-6947d4b546-xwnsh” is waiting to start: CreateContainerConfigError
Request your help and suggestions to resolve this issue.
Regards,
Ganesh Kumar K
Hello @Ganesh1305,
Could you please share more details about the issue you’re facing?
It would be helpful if you could describe the pod status and any related events or errors observed. This will help us assist you more effectively.
If you are not getting any recent events, Just restart the pod.
Best Regards
Team MOSIP