I think I have interesting use case so I would like to hear advices of the people with more knowledge. I have my App ("ads") which works in Kubernetes without any issue. It runs on port 9000. It has args which have its instance name (serverName) and in the list of servers it has reference ..
I need to make my Linux container running (without any app or service in it) so I can enter /bin/bash and modify some local linux files before I actually manually run my app from the container shell (this is purely for some debugging purposes so I do not want any modifications in my image itself, ..
Firstly I succesfully mounted, my Linux path on Pod. I used azure file share and mounted folders appear on File Share. volumeMounts: – name: ads-filesharevolume mountPath: /opt/front/arena/host volumes: – name: ads-filesharevolume azureFile: secretName: fa-fileshare-secret shareName: faselectaksshare readOnly: false Now on File Share I added one subfolder "windows" for mounting, in logs it mentions it is ..
in regular setup, without Docker container I have the following use case: I install App1 Run Database Command from my server to insert required rows in database before the App1 is started OR run the App2 which is installed on some other server and run App2 specific command with some predefined script before the App1 ..
I have Azure Kubernetes Service cluster and I have VM outside the cluster, from different virtual network, from which I try to connect to my container Pod App which is being run on TCP Port 9000. I must not use Public IP and That is not HTTP connection, but I need to connect using the ..
I have Linux Kubernetes Node with CNI networking. Two Pods are on that one Node in the same virtual network. Pod1 with container1 has deployment name "test1" and port 9000. Pod2 with container2 has deployment name "test2" and needs to connect to test1 and its port 9000. apiVersion: apps/v1 kind: Deployment metadata: name: test2 labels: ..
We deployed our app, Pod and Service in Azure Kubernetes Service but we cannot connect to our container app from the VM from another Virtual Network. It seems that Service Type internal load balancer cannot be used for those purpose when we want to establish network connection from Azure resource (VM) from another Virtual Network/SubNet, ..
I deployed my first container, I got info: deployment.apps/frontarena-ads-deployment created but then I saw my container creation is stuck in Waiting status. Then I saw the logs using kubectl describe pod frontarena-ads-deployment-5b475667dd-gzmlp and saw MountVolume error which I cannot figure out why it is thrown: Warning FailedMount 9m24s kubelet MountVolume.SetUp failed for volume "ads-filesharevolume" : ..
From Azure we try to create container using the Azure Container Instances with prepared YAML. From the machine where we execute az container create command we can login successfully to our private registry (e.g fa-docker-snapshot-local.docker.comp.dev on JFrog Artifactory ) after entering password and we can docker pull it as well docker login fa-docker-snapshot-local.docker.comp.dev -u svc-faselect ..
I have in docker-compose YAML the following command segment: command: – /opt/sbin/demo_start – demo_start – ‘-unicode’ – ‘-db_server test01’ I now need to convert that into YAML format for K8S, but I am really not sure how this should be done. command: ["/opt/sbin/demo_start"] args: ["demo_start", "-unicode","-db_server test01"] p.s.- unfortunately I cannot test it, I need ..