Join GitHub today
GitHub is home to over 36 million developers working together to host and review code, manage projects, and build software together.Sign up
Error parsing command-line arguments in 1.3.0 #1647
What were you doing?
Attempting to run version 1.3.0 in a Docker container. Here's an example Dockerfile:
FROM python:2.7-slim RUN apt-get update \ && apt-get install -y build-essential git \ && git clone -b 1.3.0 https://github.com/foosel/OctoPrint.git \ && cd OctoPrint \ && python setup.py install CMD ["octoprint"]
What did you expect to happen?
What happened instead?
Running without arguments also yields the same result.
Branch & Commit or Version of OctoPrint
Printer model & used firmware incl. version
Browser and Version of Browser, Operating System running Browser
Docker on x86 as well as arm (a raspberry pi).
Link to octoprint.log
Link to contents of terminal tab or serial.log
Screenshot(s) showing the problem:
I have read the FAQ.
It looks like there is some information missing from your bug report that will be needed in order to solve the problem. Read the Contribution Guidelines which will provide you with a template to fill out here so that your bug report is ready to be investigated (I promise I'll go away then too!).
If you did not intend to report a bug but wanted to request a feature or brain storm about some kind of development, please take special note of the title format to use as described in the Contribution Guidelines.
Also make sure you are at the right place - this is the bug tracker of the official version of OctoPrint, not the Raspberry Pi image OctoPi nor any unbundled third party OctoPrint plugins or unofficial versions. Make sure too that you have read through the Frequently Asked Questions and searched the existing tickets for your problem - try multiple search terms please.
I'm marking this one now as needing some more information. Please understand that if you do not provide that information within the next two weeks (until 2016-12-25 22:10 UTC) I'll close this ticket so it doesn't clutter the bug tracker. This is nothing personal, so please just be considerate and help the maintainers solve this problem quickly by following the guidelines linked above. Remember, the less time the devs have to spend running after information on tickets, the more time they have to actually solve problems and add awesome new features. Thank you!
PS: I'm just an automated script, not a human being, so don't expect any replies from me :) Your ticket is read by humans too, I'm just not one of them.
Testing the same command on OctoPi:
Same behaviour on any other checkout, regardless of OS.
Also tried a replication of your exact checkout & install steps. Differences being: no docker, virtual environment:
The error sounds like something seriously messed up the command line arguments here.
Now, I have to admit that I'm completely unfamiliar with Docker, and especially how it works internally, but could it be that it's doing something in its environmental setup or they way the actual executable gets called that's messing with things here?
I played around a bit with things and finally could reproduce the exact error message:
Could it be that such an environment variable is set by Docker, causing the issues here? Should be easy enough to check with
For the record, with above commit I cannot reproduce anymore:
That is available on the
Would still be important to know if that was actually the reason behind this in the Docker environment and why that var was even set.