Packer Docker builder using chmod on Windows 10 -


here packer file:

    {         "builders": [{             "type": "docker",             "image": "ubuntu",             "export_path": "image.tar"         }],         "provisioners": [{             "type": "shell",             "inline": ["mkdir /full_install",             "mkdir /scripts"]         },         {             "type": "file",             "source": "./scripts/",             "destination": "/scripts"         }]     }

simple. trying make 2 directories , upload scripts 1 of directories. getting following output on windows 10:

c:\work\packer\mypacker>packer build myserver.json docker output in color.

==> docker: creating temporary directory sharing data... ==> docker: pulling docker image: ubuntu docker: using default tag: latest docker: latest: pulling library/ubuntu docker: digest: sha256:dd7808d8792c9841d0b460122f1acf0a2dd1f56404f8d1e56298048885e45535 docker: status: image date ubuntu:latest ==> docker: starting docker container... docker: run command: docker run -v c:\users\syarnell\appdata\roaming\packer.d\tmp\packer-docker346952011:/packer-files -d -i -t ubuntu /bin/bash docker: container id: 84a0969874bbfc031f60ad03c8e6765f895733cdfd51c727ae59c82a80c82658 ==> docker: provisioning shell script: c:\users\syarnell\appdata\local\temp\packer-shell141617915 ==> docker: uploading ./scripts/ => /scripts ==> docker: killing container: 84a0969874bbfc031f60ad03c8e6765f895733cdfd51c727ae59c82a80c82658 build 'docker' errored: chmod c:\users\syarnell\appdata\roaming\packer.d\tmp\packer-docker346952011\dirupload432828853\batchinstall.sh: not supported windows

==> builds didn't complete , had errors: --> docker: chmod c:\users\syarnell\appdata\roaming\packer.d\tmp\packer-docker346952011\dirupload432828853\batchinstall.sh: not supported windows

==> builds finished no artifacts created.

c:\work\packer\mypacker>

why trying chmod file in windows 10?

packer docker builder doesn't work on windows, open issue on github.com.


Comments

Post a Comment

Popular posts from this blog

Command prompt result in label. Python 2.7 -

i want put result(output) of shell command label. command works, label shows "0", however, in command prompt, result shown correctly, need showed in label. doing ubuntu. myg1 = button(root, text="rodyti informacija", command=lambda: gauti()) myg1.pack(side=bottom) def gauti(): imti = tekstas.get("1.0", "end-1c") info = subprocess.call("id '{imti}' ".format(imti=imti), shell=true) w = label(root, text= info) w.pack(side = bottom) subprocess.call() returns exit code of process created (in case 0 success). if want text output of process, should instead call subprocess.check_output() .
Read more

javascript - How do I use URL parameters to change link href on page? -

i change href value of link using url parameters. example: default <a id="dlink" href="link-1">link</a> but, when user goes https://url.com/?dlink=link-2 it swaps out link new link <a id="dlink" href="link-2">link</a> first need value url. if you're not using javascript framework can create function using jquery. please check get url parameter jquery or how query string values in js it. after that, element "a" id , set value there. $("#dlink").attr("href", hreffromparam);
Read more

amazon web services - AWS Route53 Trying To Get Site To Resolve To www -

so have domain nameservers pointed aws route 53. site hosted on ec2 instance , reachable resolves site.com, if input www.site.com. i'm curious how site resolve www.site.com. have under route53 domains hosted zone 2 additional record sets outside of ns , soa: a site.com ec2 elastic ip cname www.site.com ec2 public dns i can reach site using both site.com , www.site.com, resolve site.com. there way make if enter either, resolves www.site.com? at first, both should record set. a site.com ec2 elastic ip www.site.com ec2 elastic ip and need redirect setting in web server (nginx, apache, ..) following. (source: how redirect www non-www nginx on centos 7 ) redirect non-www www if want redirect users plain, non-www domain www domain, add server block: server { server_name example.com; return 301 $scheme://www.example.com$request_uri; } save , exit. configures nginx redirect requests "example.com" "www.example.com". not...
Read more