Hello Rob,

Thanks for your reply.

I tried `docker run myusername/apache -v /home/core/share:/var/www/html/` 
and receive this error:
"exec: "-v": executable file not found in $PATH
docker: Error response from daemon: oci runtime error: exec: "-v": 
executable file not found in $PATH."

Any ideas what I am missing?

Cheers,
Michael


On Tuesday, January 3, 2017 at 9:40:51 AM UTC-8, Rob Szumski wrote:
>
> Have you tried `docker run blah -v /home/core/share:/var/www/html/`? The 
> second path is inside the container.
>
>  - Rob
>
> On Dec 31, 2016, at 3:04 PM, Michael Chavez <[email protected] 
> <javascript:>> wrote:
>
> Hello CoreOS Dev Google Group,
>
> I am a super noob. 
>
> I got CoreOS running on my Macbook using Vagrant. I am able to get the 
> Apache2 Ubuntu Default Page. What I want to do for example, is being able 
> to modify/replace the file at /var/www/html/index.html. Later I want to use 
> the technique to develop Node.js and WordPress apps locally and deploy to 
> remote webservers, ala "Cloud Native" style.
>
> I am able to have files shared from local directory on my Macbook to the 
> CoreOS by adding/uncommenting this from the Vagrant file:
>       config.vm.synced_folder ".", "/home/core/share", id: "core", :nfs => 
> true, :mount_options => ['nolock,vers=3,udp']
> That works in syncing the "share" folder inside CoreOS running inside of 
> Vagrant to my local directory on Macbook, but I can't figure out how to get 
> that to sync to the container inside of CoreOS running Ubuntu with Apache. 
>
> I've been following these tutorials:
> https://coreos.com/os/docs/latest/booting-on-vagrant.html
> https://github.com/coreos/coreos-vagrant
> https://coreos.com/os/docs/latest/getting-started-with-docker.html
> https://docs.docker.com/engine/tutorials/dockervolumes (this is where 
> things don't work for me)
>
> I am going about this the right way? Should I just use Docker for Mac and 
> cut the CoreOS on Vagrant out (I don't want to necessarily do that)? 
>
> Any help would be greatly appreciated!
>
> Thanks and happy new years!
>
> Cheers,
> Michael
>
>
>

Reply via email to