Hello
I was able to run the software, with the exact docker command line that you
wrote.
I just used a stock configuration file (config/default-config.xml file from
the Ignite 2.7.0 tarball), copied in $PWD as ignite-config.xml (as called
in your example)
Please double check to have the proper configuration file in $PWD, and the
name of the file itself.
Best regards
Gianluca Bonetti
Il giorno mer 3 apr 2019 alle ore 14:31 Coleman, JohnSteven (Agoda) <
johnsteven.cole...@agoda.com> ha scritto:
> I’d like to pass a local configuration file to docker as below, but ignite
> doesn’t find it, any ideas? The file is in the PWD directory. Using windows
> powershell.
>
>
>
> *docker *run *-it *--rm --net=host *-v *${PWD}*:/apache-ignite/config **-e
> **"CONFIG_URI=file:///apache-ignite/config/ignite-config.xml" *--name
> ignite apacheignite/ignite
>
>
>
>
>
> /opt/ignite/apache-ignite/bin/ignite.sh, WARN: Failed to resolve JMX host
> (JMX will be disabled): linuxkit-00155d0f670e
>
> class org.apache.ignite.IgniteException: Failed to instantiate Spring XML
> application context
> [springUrl=file:/apache-ignite/config/ignite-config.xml, err=IOException
> parsing XML document from URL
> [file:/apache-ignite/config/ignite-config.xml]; nested exception is
> java.io.FileNotFoundException: /apache-ignite/config/ignite-config.xml (No
> such file or directory)]
>
> at
> org.apache.ignite.internal.util.IgniteUtils.convertException(IgniteUtils.java:1025)
>
> at org.apache.ignite.Ignition.start(Ignition.java:351)
>
> at
> org.apache.ignite.startup.cmdline.CommandLineStartup.main(CommandLineStartup.java:301)
>
> Caused by: class org.apache.ignite.IgniteCheckedException: Failed to
> instantiate Spring XML application context
> [springUrl=file:/apache-ignite/config/ignite-config.xml, err=IOException
> parsing XML document from URL
> [file:/apache-ignite/config/ignite-config.xml]; nested exception is
> java.io.FileNotFoundException: /apache-ignite/config/ignite-config.xml (No
> such file or directory)]
>
> --
> This message is confidential and is for the sole use of the intended
> recipient(s). It may also be privileged or otherwise protected by copyright
> or other legal rules. If you have received it by mistake please let us know
> by reply email and delete it from your system. It is prohibited to copy
> this message or disclose its content to anyone. Any confidentiality or
> privilege is not waived or lost by any mistaken delivery or unauthorized
> disclosure of the message. All messages sent to and from Agoda may be
> monitored to ensure compliance with company policies, to protect the
> company's interests and to remove potential malware. Electronic messages
> may be intercepted, amended, lost or deleted, or contain viruses.
>