fs-service | Fax and Voice Message API Solution with FreeSWITCH | TCP library

I created a nfs server in a pod to use it as a volume. When creating another pod with a volume, the volume mount does work with the ip of the nfs pod. Since this ip is not guaranteed to stay the same, I added a service for my nfs pod and added a fixed cluster ip. When starting the container with the volume mount, it always fails with the following error:

Unable to mount volumes for pod "nginx_default(35ecd8ec-a077-11e8-b7bc-0cc47a9aec96)": timeout expired waiting for volumes to attach or mount for pod "default"/"nginx". list of unmounted volumes=[nfs-demo]. list of unattached volumes=[nfs-demo nginx-test-account-token-2dpgg]

I have a docker image (lfs-service:latest) that I'm trying to run as part of a suite of micro services.

• RHELS 7.5
• Docker version: 1.13.1
• docker-compose version 1.23.2
• Postgres 11 (installed on RedHat host machine)

The following command works exactly as I would like:

I recently upgraded from on-prem TFS 2013 to TFS 2017 (update 3). As part of the upgrade \ migration to new servers we switched from using port 8080 to port 443 (https).

We have an old RHEL 6.8 machine which we've been using as a build server for a small number of Java projects using Git. The server is running git 1.7.1 (which ships with RHEL 6) and we are no longer able to clone \ pull \ push the Git repos hosted in TFS.

FYI - I'm using export GIT_CURL_VERBOSE=1 to beef up the logging.

My initial problem was that Git didn't trust the certificate from my company's internal CA. (Peer's certificate issuer is not recognized) I fixed that by adding the internal cert to my ca-bundle.crt.

With that resolved I now get a 401 Unauthorized error that I cannot figure out. I am able to use cURL to authenticate to the exact same URLs as long as I provide the --ntlm switch. Git appears to be using NTLM but for whatever reason it refuses to work.

I have a kubernetes cluster running on google container engine that defines a Pod running a NFS-Server, which I want to access in other Pods via various PersistentVolumes.

What is the best way to configure the NFS Service, if it is in the same cluster?

According to various documentation ive found its not possible to rely on kube-dns for this, because the node starting the kubernetes pod is not configured to use it as its DNS.

So this is out of question (and really does not work - ive tested it, with various different hostname/FQDN...)

In this repository https://github.com/mappedinn/kubernetes-nfs-volume-on-gke I am trying to share a volume through NFS service on GKE. The NFS file sharing is successful if hard coded IP address is used.

But, in my point of view, it would be better to use DNS name in stead of hard coded IP address.

Below is the declaration of the NFS service being used for sharing a volume in Google Cloud Platform:

Machine - MAC bookPro Mac OSx 10.11.6

Docker - Docker for mac Docker version 17.03.1-ce, build c6d412e

VirtualBox - Version 5.1.22 r115126 (Qt5.6.2)

I have my AEM (CMS) running on an image on Virtual Box, provisioned using Vagrant + Chef. We allocate IP explicitly to the box - 192.168.x.x

We have introduced a Microservice (Spring boot + MySQL) that we wish to deploy using Docker. On my local (MAC) I successfully get Microservice up and running and two docker instances (Microservice, MySQL) connecting to each other successfully. The Microservice exposes certain end-points that I need to invoke from my AEM running in Virtual box. This is something I am not able to do, My virtualbox instance is not able to connect to docker hosted app (the ip of docker machine is not accessible within my virtualbox)

I use docker compose to get my docker instances working -

Here is my docker-compose.yml