Notice of wrong startup string but correct processing.

[pomazanbohdan]

docker-compose.yml:

services:
  garnet:
    image: yzy613/garnet:latest
    # image: altall/garnet:v1.0.0
    container_name: garnet
    command:
      /app/GarnetServer.exe --config-import-path /data/config/garnet.json

garnet | _________
garnet | /||_||\ Garnet 1.0.1 64 bit; standalone mode
garnet | '. \ / .' Port: 3278
garnet | '.\ /.' https://aka.ms/GetGarnet
garnet | '.'
garnet |
garnet | 08::40::57 info: GarnetServer[0] Garnet 1.0.1 64 bit; standalone mode; Port: 3278
garnet | 08::40::57 info: ArgParser[0] Configuration import from embedded resource succeeded. Path: defaults.conf.
garnet | 08::40::57 warn: ArgParser[0] The following command line arguments were not parsed: /app/GarnetServer.exe. Please check the syntax of your command. For detailed usage information run with --help.
garnet | 08::40::57 info: ArgParser[0] Configuration import from local machine succeeded. Path: /data/config/garnet.json.

[y1jiong]

I noticed that the docker-compose.yml you used contains command. The original Dockerfile uses ENTRYPOINT, so the content of command is appended to ENTRYPOINT. As a result, it can work normally and issue warnings at the same time.

Here, I recommend leaving command empty.

In addition, this image¹ currently only supports Linux amd64 and does not support Windows.

Footnotes

1. yzy613/garnet ↩

[pomazanbohdan]

yes, I'm using my own startup options, since I have to specify a config file.

Usually, other products do not issue errors in this case.

Of course, it is better to use env parameters, but I understand that they are not supported

[y1jiong]

If you only need to specify the configuration file, you only need to fill in --config-import-path /data/config/garnet.json in the command.

[pomazanbohdan]

need to fill in --config-import-path /data/config/garnet.json in the command

Thx. Work