Skip to content
This repository has been archived by the owner on Feb 24, 2020. It is now read-only.

set-working-directory #209

Open
farazfazli opened this issue May 18, 2016 · 4 comments
Open

set-working-directory #209

farazfazli opened this issue May 18, 2016 · 4 comments

Comments

@farazfazli
Copy link
Contributor

farazfazli commented May 18, 2016

Hello,

Mounting volumes didn't work for me until I used acbuild set-working-directory...is this needed to mount volumes when building ACIs? I didn't see it in the NGINX example and would appreciate some info showing exactly when and under which setting the working directory is needed. Possibly I just missed something when running my acbuild commands which is why I needed to add it.

Thank you!

@jonboulle
Copy link
Contributor

I don't really see why that should be necessary. What happened when you didn't have it provided?

@farazfazli
Copy link
Contributor Author

farazfazli commented May 19, 2016

@jonboulle The container wasn't able to write to or read from the files in the location I mounted to. I didn't change anything except set the working directory.

@jonboulle
Copy link
Contributor

ok, I bet @dgonyeo can investigate :-)

On Thu, May 19, 2016 at 6:06 PM, Faraz Fazli [email protected]
wrote:

@jonboulle https://github.com/jonboulle The container wasn't able to
write to or read to the files in the location I mounted to. I didn't change
anything except set the working directory.


You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
#209 (comment)

@cgonyeo
Copy link
Member

cgonyeo commented Jun 13, 2016

Sorry about the lengthy delay, school was ending and things were very hectic. This sounds very interesting though, is there any chance you still have an acbuild script and/or the ACIs that exhibited this behavior? acbuild set-working-directory shouldn't impact how mounts work at all.

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

No branches or pull requests

3 participants