Made changes to Atomic App instructions, run command in response to #282
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
|
||
| ``` | ||
| cd /path/to/atomic-site/ | ||
| sudo atomicpp run Nulecule/ |
Contributor
There was a problem hiding this comment.
typo, should be atomicapp
Contributor
|
Thanks Josh, works for me now! (gotta say that volume management with atomicapp is not so easy to figure out at first glance) |
Contributor
Author
|
Volumes? Can you explain them to me? ;-) |
Contributor
|
When I got asked about paths to sources and data; I had no idea what I should put there (on third attempt I figured out it's suppose to be |
Contributor
Author
|
Tomas: part of the problem is that the Nulecule spec for Volumes has not been merged: projectatomic/nulecule#203 |
Contributor
|
Thanks for the pointer. Yep, it seems that's it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
issue #274
Tomas, please try the updated instructions and docker-run command to see if it fixes the run for you.
@TomasTomecek