Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Multiple azure-file-volume-share-name and azure-file-volume-mount-path pairs support #62

Closed
NachoVazquez opened this issue Oct 2, 2021 · 3 comments

Comments

@NachoVazquez
Copy link

The Problem

I'm trying to run a container that has multiple volumes mounts.

For example, my docker-compose would look something like:

version: '3.8'

services:
  my-container:
    image: my-container-image
    ports:
      - 3001:3001
      - 3333:3333
    environment:
      - SOME_ENV=<env-value>
    volumes:
      - vol1_host:/vol1
      - vol2_host:/vol2

volumes:
  vol1_host:
  vol2_host:

I've created two Azure Storage Shares vol1_host and vol2_host using the same Azure Storage Account.

Now I need to connect my two volumes using the aci-deploy action, but I can not find any example of what is the syntax for multiple volumes.

How to support multiple pairs of azure-file-volume-share-name and azure-file-volume-mount-path?

@NachoVazquez
Copy link
Author

Reading the docs, I understand that the design of this action was following the capabilities of the Azure CLI and that more complex scenarios need a config .yml file.

Probably the answer to this problem is not to actually add support for the multiple volumes directly but to add support for a config file parameter.

@kanika1894
Copy link
Contributor

Closing this as this seems to be a duplicate for #63

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants