VMM-Mtech

`-E space:_` and using _ instead of spaces seems to work, but this is deprecated. That's why I created this issue

`docker run -v %cd%/reports:/opt/robotframework/reports:Z -v %cd%/robot:/opt/robotframework/tests:Z -e ROBOT_OPTIONS="--loglevel DEBUG --extension robot -v MY_VARIABLE:This\ with\ spaces" my_docker_image [ ERROR ] Parsing 'with\' failed: File or directory to execute does not exist.`

Even worse. `docker: invalid reference format: repository name must be lowercase.` And as far as I know, we can't just drop double quotes from ROBOT_OPTIONS since we want to inject...

If I looked at your code correctly, docker will run the run-tests-in-virtual-screen.sh script, right? Could you test if you could do some escaping or something there?

`docker run -v %cd%/reports:/opt/robotframework/reports:Z -v %cd%/robot:/opt/robotframework/tests:Z -e ROBOT_OPTIONS="--loglevel DEBUG --extension robot -v \"MY_VARIABLE:This with spaces\"" my_docker_image` `[ ERROR ] Parsing 'with' failed: File or directory to execute does not exist.`

Hi, refreshing this one. The escape (or -E) worked with 3.6.0, but does not work at all with 3.7.0. ``` docker run -v %cd%/reports:/opt/robotframework/reports:Z -v %cd%/robot:/opt/robotframework/tests:Z -e ROBOT_OPTIONS="--loglevel DEBUG --extension...

I'm not convinced that the fix PapsOu suggested will solve the whole issue since my issue was with RF itself and not the chrome in the container.

To me it seems that there are no entrypoints in this dockerfile to run the rebot command at all. So although you can give REBOT_OPTIONS, the rebot command is never...

Updating the situation: We finally were forced to update to v. 3.8.0, where we couldn't use the -E flag anymore. So our workaround now is to pass the variables with...

Hi! I'm not sure if our issue is exactly the same as yours, but there are some similarities... EDIT: We're using timescale 2.8.1 on PG 12. We have ~100M+ rows...