Score:0

Allow Bitbucket pipeline runner to access ports other than 80 and 443 such as NFS

ao flag

I am trying to persuade a bitbucket pipeline that employs a runner on our GKE based infrastructure to mount a directory from a GCE VM via NFS.

It seems that the outgoing traffic to NFS ports is blocked.

The pipeline has no problem accessing port 443 on an external web server.

No incoming traffic is visible to tcpdump on the NFS server.

Firewall logs show nothing being blocked.

The underlying runner containers (bb-k8s-runner and docker-in-docker) are both able to mount NFS directories from the server.

I'm wondering if anybody has a tip to enable the pipeline to access files on the NFS server.

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.