Could you provide a packer only repo? I have a hard time understanding where this comes from. But I expect that your tool or test somewhere provides packer with a path containing a unexpanded path with ~ which is a shell-ism.
On 17 March 2018 at 15:01, thomas.lehmann.private via Packer < [email protected]> wrote: > Hi, > > I'm author of the tool spline: https://github.com/Nachtfeuer/pipeline > I'm working on extending spline for a packer task like following: > > $ cat examples/packer.yaml > model: > image: centos:7 > > pipeline: > - stage(Example): > - tasks(ordered): > - packer: > script: | > { > "builders": [{ > "type": "docker", > "image": "{{ model.image }}", > "commit": true, > "changes": [ > "LABEL pipeline={{ env.PIPELINE_PID }}", > "LABEL pipeline-stage={{ env.PIPELINE_STAGE > }}" > ] > }], > > "provisioners": [{ > "type": "shell", > "inline": [ > "yum -y install python-setuptools", > "easy_install pip", > "pip install tox" > ] > }], > > "post-processors": [{ > "type": "docker-tag", > "repository": "spline/packer/demo", > "tag": "0.1" > }] > } > > > This works fine. However ... when coming to unit/regression tests I > detected following issue: > > Running via tox (wrapper for Python virtual environment) the unittest for > the Packer task the Packer build complains about this: > *~/.packer.d/tmp/packer-docker735583400" includes invalid characters > for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed* > > I also can run the one test without tox and no problem arrives: > * PYTHONPATH=$PWD python -m unittest discover -v -s tests -p > "test_packer.py"* > > The Packer build command is following: > *packer build -parallel=true -on-error=cleanup /tmp/packer-USh6y4.json* > > Is it possible to tell packer to use another root path like current folder > or /tmp without special characters? > (ot at least it should be ensured that the full path is used) > > I'm uisng Packer 1.2.1 and Docker 17.12.1-ce > > Regards, > Thomas > > My question now: what can I d > > > -- > This mailing list is governed under the HashiCorp Community Guidelines - > https://www.hashicorp.com/community-guidelines.html. Behavior in > violation of those guidelines may result in your removal from this mailing > list. > > GitHub Issues: https://github.com/mitchellh/packer/issues > IRC: #packer-tool on Freenode > --- > You received this message because you are subscribed to the Google Groups > "Packer" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/packer-tool/359c57a5-e8e5-4256-9354-54a2cf7cc26e%40googlegroups.com > <https://groups.google.com/d/msgid/packer-tool/359c57a5-e8e5-4256-9354-54a2cf7cc26e%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- This mailing list is governed under the HashiCorp Community Guidelines - https://www.hashicorp.com/community-guidelines.html. Behavior in violation of those guidelines may result in your removal from this mailing list. GitHub Issues: https://github.com/mitchellh/packer/issues IRC: #packer-tool on Freenode --- You received this message because you are subscribed to the Google Groups "Packer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/packer-tool/CALz9Rt-yKSFYuwd1wT0-Wd5-PTWtnYcZdMcjPBKyq68LCZzDHw%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
