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

dockerForm task doesn't use relative paths #399

Open
davidawad opened this issue Mar 17, 2021 · 0 comments
Open

dockerForm task doesn't use relative paths #399

davidawad opened this issue Mar 17, 2021 · 0 comments

Comments

@davidawad
Copy link

This is perhaps more of a feature request, but right now when the dockerform task generates a docker-compose file it uses the full path, which means that this docker-compose configuration isn't portable to another machine.

version: '3'
services:
  notary:
    volumes:
    - /Users/davidawad/Desktop/samples-java/Features/customlogging-yocordapp/build/nodes/Notary/node.conf:/etc/corda/node.conf
    - /Users/davidawad/Desktop/samples-java/Features/customlogging-yocordapp/build/nodes/Notary/certificates:/opt/corda/certificates
    - /Users/davidawad/Desktop/samples-java/Features/customlogging-yocordapp/build/nodes/Notary/logs:/opt/corda/logs

It would be quite nice if there was an option to just have it output the relative paths in order for the configuration to be portable to another machine if someone wanted to do that.

version: '3'
services:
  notary:
    volumes:
    - ./Notary/node.conf:/etc/corda/node.conf
    - ./Notary/certificates:/opt/corda/certificates
    - ./Notary/logs:/opt/corda/logs
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