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

Use path within named volume once available #80

Open
nuest opened this issue Dec 12, 2017 · 1 comment
Open

Use path within named volume once available #80

nuest opened this issue Dec 12, 2017 · 1 comment
Assignees

Comments

@nuest
Copy link
Member

nuest commented Dec 12, 2017

As described here, named volumes cannot be combined with paths within the volume.

This is required in muncher to mount the correct path to 2nd level containers when using a named volume with docker-compose, see source code occurences of config.fs.volume. The problem only occurs when mounting a specific path within the volume (i.e. manifest generation, metadata brokering after save in muncher), mounting the volume to the data directory (o2rplatform_o2rstorage:/tmp/o2r) to the 2nd-level container seems to work fine (metadata extraction and brokering in loader for example) when it is possible to provide the correct path to the tool in the 2nd-level container.

When moby/moby#32582 is closed, updated the respective FIXMEs.

@nuest nuest self-assigned this Dec 12, 2017
@nuest
Copy link
Member Author

nuest commented Dec 12, 2017

TODO Try out if the same approach that works for metadata also works for manifest generation! Probably must extend containerit a bit for that.

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

No branches or pull requests

1 participant