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

fix(Dockerfile): Navigate Docker's wonky COPY command. #200

Merged
merged 1 commit into from Apr 7, 2017

Conversation

jtk54
Copy link
Contributor

@jtk54 jtk54 commented Apr 7, 2017

I tested this locally on a Docker container and verified that
the config directory structure looks how we actually want it to this
time. @duftler FYI. Sorry for the repeated attempts to solve this.

I tested this locally on a Docker container and verified that
the config directory structure looks how we actually want it to this
time.
@jtk54
Copy link
Contributor Author

jtk54 commented Apr 7, 2017

COPY <from> <to>

Apparently when to is a directory that doesn't exist yet on a container, COPY makes a directory when from is a directory. When to does exist, COPY copies the files in from into to and doesn't actually create a from directory in to. That's a least my understanding of the way this thing behaves. Not consistent with linux cp.

@jtk54 jtk54 merged commit 358ab4f into spinnaker:master Apr 7, 2017
opsmxdemo pushed a commit to OpsMx/rosco that referenced this pull request Sep 15, 2020
I tested this locally on a Docker container and verified that
the config directory structure looks how we actually want it to this
time.
opsmxdemo pushed a commit to OpsMx/rosco that referenced this pull request Sep 16, 2020
I tested this locally on a Docker container and verified that
the config directory structure looks how we actually want it to this
time.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant