0

I've got a pipeline building an RPM package which I'd like to upload to our Nexus server. The Nexus server runs on an ACI (Azure Container Instance). The ACI is using a private network.

IF I've got it right the intended way is:

  1. Create a Generic service connection containing the url, credentials and root directory of the ACI.
  2. Use the cUrl task to select the file and use the Generic service to perform the upload.

The problem however is that the pipeline vm can not connect to the ACI (no route to host).

Can somebody help me to fix this ? Or give me pointers to online resources ?

JG801
  • 121
  • 2
  • 7

1 Answers1

0

As I know, when you create the ACI in the private network, it means you cannot access it outside directly. But you can use the Azure Application Gateway to access the ACI by adding the private IP address to the backend. And you can also use this way to upload files to the ACI.

And there is also another way to upload files to the ACI in the private network. In this way, you need to mount the Azure File Share to the ACI in the creation time and then you can upload files to that Azure File Share. You can access these files in the mount point of the ACI. I recommend this way more than others.

Charles Xu
  • 29,862
  • 2
  • 22
  • 39
  • I'll have a look into Azure Application Gateway. The ACI already has a storage account mounted. I thought about copying the file this way. Assuming this works, I still need to call Nexus to update its indices. Same problem. – JG801 Jun 02 '20 at 06:49
  • @JG801 It means your real issue is to access the ACI in the VNet, not upload files to the ACI. Anyway, all the ways to achieve it are contained in the answer. And if it works for you please accept it as the answer. – Charles Xu Jun 02 '20 at 06:54
  • @JG801 Any more questions? Does it solve your problem? – Charles Xu Jun 08 '20 at 06:12
  • We finally managed to make it working with a custom build agent located in the same network. Because according to my colleagues the gateways are only for public access. While our repositories are strictly private. – JG801 Jun 09 '20 at 07:15
  • @JG801 Your problem is to connect the ACI in the VNet from the pipeline, as I know the pipeline should connect from the Internet to the ACI. So I give you the solution for it. – Charles Xu Jun 09 '20 at 07:22
  • @JG801 So if the answer works for the question which you asked above, please accept it. – Charles Xu Jun 09 '20 at 07:29