iSharkFly-Docs
/
packer-cn
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

remove outdated comment about docker behavior

This commit is contained in:
Matthew Hooker 2017-10-03 16:47:30 -07:00
parent bafcf7dfb1
commit e26df7ebb3
No known key found for this signature in database
GPG Key ID: 7B5F933D9CE8C6A1
1 changed files with 1 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

5
website/source/docs/provisioners/file.html.md
View File

@ -57,10 +57,7 @@ know.
First, the destination directory must already exist. If you need to create it,
use a shell provisioner just prior to the file provisioner in order to create
the directory. If the destination directory does not exist, the file
provisioner may succeed, but it will have undefined results. Note that the
`docker` builder does not have this requirement. It will create any needed
destination directories, but it's generally best practice to not rely on this
behavior.
provisioner may succeed, but it will have undefined results.
Next, the existence of a trailing slash on the source path will determine
whether the directory name will be embedded within the destination, or whether