Getting started docker example fails due to relative path

[m-adams]

Bug Description

Following the Docker getting started in the Readme fails.
The Docker error relates to the mounting of the configuration fail.

This is on MacOS

The error message is
docker: Error response from daemon: create ./crawl-config.yml: "./crawl-config.yml" includes invalid characters for a local volume name, only "[a-zA-Z0-9][a-zA-Z0-9_.-]" are allowed. If you intended to pass a host directory, use absolute path.

I fixed the error using
docker run \
-v "$(pwd)"/crawl-config.yml:/crawl-config.yml \
-it docker.elastic.co/integrations/crawler:latest jruby bin/crawler crawl /crawl-config.yml

To Reproduce

Steps to reproduce the behavior:

1. Run
   open-crawler % docker run
   -v ./crawl-config.yml:/crawl-config.yml
   -it docker.elastic.co/integrations/crawler:latest jruby bin/crawler crawl /crawl-config.yml

Expected behavior

getting started examples need to be robust and work

Environment

MacOS, Docker Desktop

[seanstory]

@m-adams I can't reproduce.

$ docker run -v ./crawl-config.yml:/crawl-config.yml -it docker.elastic.co/integrations/crawler:latest jruby bin/crawler crawl /crawl-config.yml
[crawl:68387bb0c115d93b976a54f4] [primary] Initialized an in-memory URL queue for up to 10000 URLs
[crawl:68387bb0c115d93b976a54f4] [primary] ES connections will be authorized with configured username and password
[crawl:68387bb0c115d93b976a54f4] [primary] ES connections will use SSL without ca_fingerprint

$ docker --version
Docker version 27.4.0, build bde2b89

Docker Desktop version: 4.37.2 (179585)

I'm also using Bash shell, instead of the default ZSH, which I wouldn't expect to be an issue, but perhaps wrapping your CLI args in quotes would help?

[m-adams]

It looks like this is a docker cli version issue.
My docker desktop and daemon were up to date but my CLI was older
Docker version 20.10.17, build 100c70180f

I've upgraded
Docker version 28.2.1, build 879ac3f88f

Now I don't get the error.
We may still want to consider using the absolute path in the example as it is more robust to CLI version. I con't be the only person that doesn't actively upgrade the docker cli.