Add variabels and enviroments to docker

[geiraage]

I tried to add example like parameters on hub.docker.com like e= but it dosnt work.

It should have maybe have a volume (v:) for config or enviroments (e:) directly in docker run . There should at least be a volume options for logs.

-alsologtostderr
log to standard error as well as files
-conn_type string
Connection type. Possible values are tcp, tcp4, tcp6 (default "tcp")
-enable_prometheus
Enable prometheus
-geoip_supplier string
Supplier to obtain Geohash of IPs. Possible values are "off", "ip-api", "max-mind-db" (default "off")
-host string
SSH listening address (default "0.0.0.0")
-interval_ms int
Message millisecond delay (default 1000)
-line_length int
Maximum banner line length (default 32)
-log_backtrace_at value
when logging hits line file:N, emit a stack trace
-log_dir string
If non-empty, write log files in this directory
-log_link string
If non-empty, add symbolic links in this directory to the log files
-logbuflevel int
Buffer log messages logged at this level or lower (-1 means don't buffer; 0 means buffer INFO only; ...). Has limited applicability on non-prod platforms.
-logtostderr
log to standard error instead of files
-max_clients int
Maximum number of clients (default 4096)
-max_mind_db string
Path to the MaxMind DB file.
-port value
SSH listening port. You may provide multiple -port flags to listen to multiple ports. (default "2222")
-prometheus_clean_unseen_seconds int
Remove series if the IP is not seen for the given time. Set to 0 to disable. (default 0)
-prometheus_entry string
Entry point for prometheus (default "metrics")
-prometheus_host string
The address for prometheus (default "0.0.0.0")
-prometheus_port string
The port for prometheus (default "2112")
-stderrthreshold value
logs at or above this threshold go to stderr (default 2)
-v value
log level for V logs
-vmodule value
comma-separated list of pattern=N settings for file-filtered logging

[shizunge]

I am not sure I got your question, The format is bad. Did you confuse between the argument to endlessh-go and the argument to the docker CLI?

Here is my take.

1. the README.md at the root is primary talking about endlessh-go itself, rather than docker deployment.
2. The same README.md is synced to docker hub on release.
3. A container image is provided for easier deployment. Docker is just one of the methods to deploy a container.
4. If you think we need a better docker deployment document, IMO it better goes to the example folder and you are welcome to send a pull request.

Cheers.