-
Notifications
You must be signed in to change notification settings - Fork 71
file exists error for /etc/kubernetes when running w/ local docker-based kube setup #193
Comments
We check for @jasonbrooks it doesn't look like you're running from the vagrant box. Do you have an /etc/kubernetes dir on your host or in the vagrant box? |
I'm running from a default centos 7 vagrant box, the Vagrantfile is linked above. There's no /etc/kubernetes in there, because I'm running everything in containers, w/ the project's local Docker-based installation method. |
@aweiteka @jasonbrooks would exposing |
@rtnpro I don't think it is possible to bind mount a file that is inside the container to the host (or at least I don't think it is normally done with the docker cli). @jasonbrooks this is an issue we are going to have to look at more deeply I am going to push this to the next milestone if that is ok. |
I just tried this again, and got a different, but similar error. Creating Does atomicapp have to run on a machine w/ an |
@jasonbrooks right. I'll try to figure out why it's needed (or even if it's really needed) and get back to you. |
So I now understand this problem more. Basically our code that creates the symlink will try to create the symlink twice. In the code before we get into the place where it tries to create the symlink it basically looks something like this:
If there are multiple kube artifacts then this code gets run twice and |
Note this will be handled by #368 |
actually I take it back.. the right approach is just to not create the symlink in the first place if the target doesn't exist. |
fixed in #368 |
Running the "Local Docker-based (recommended starting point)" method from the upstream project, using this Vagrantfile:
The text was updated successfully, but these errors were encountered: