Byoc tool not working | Planet Community

Hello everyone,

As I am having some issues creating and publishing a custom collection by myself, I decided to try the BYOC Tool.

Regarding versions and artifacts:

docker version of the tool is 0.6.0

github tagged versions don’t go beyond 0.2.4, although from my basic understanding of java, master is at v0.8.2

There is only a jar release for 0.2.0

The real problem is that I can’t get the docker (best version) to work. While trying to issue an ls (list) command on a collection I get the following output:

docker run sentinelhub/byoc-tool --auth-client-id="xxxxx" --auth-client-secret='xxxx' --aws-access-key-id="xxxx" --aws-secret-access-key="xxxxx" ls c81342ef-fd52-4c89-95cd-27d6fbebeb86

2022-11-25 11:00:38,169 INFO  Fmain]: Request id is byoc-tool-0.6.0-0a16bac1-0ff4-4827-9746-37c0181a46f3

2022-11-25 11:00:38,226 INFO  Fmain]: Fetching location of the collection

2022-11-25 11:00:38,416 INFO  Fmain]: Fetching an access token

2022-11-25 11:00:39,276 ERROR Rmain]: Error occurred with message "Unexpected location creo"

java.lang.RuntimeException: Unexpected location creo

        at com.sinergise.sentinel.byoctool.sentinelhub.models.ByocCollectionInfo.getDeployment(ByocCollectionInfo.java:46)

        at com.sinergise.sentinel.byoctool.ByocTool.newByocClient(ByocTool.java:102)

        at com.sinergise.sentinel.byoctool.cli.ListTilesCmd.run(ListTilesCmd.java:22)

        at picocli.CommandLine.executeUserObject(CommandLine.java:1729)

        at picocli.CommandLine.access$900(CommandLine.java:145)

        at picocli.CommandLine$RunAll.handle(CommandLine.java:2157)

        at picocli.CommandLine$RunAll.handle(CommandLine.java:2116)

        at picocli.CommandLine$AbstractParseResultHandler.execute(CommandLine.java:1935)

        at picocli.CommandLine.execute(CommandLine.java:1864)

        at com.sinergise.sentinel.byoctool.ByocTool.main(ByocTool.java:147)

Thanks

Page 1 / 1

I might add, that the S3 container is in CREODIAS. I don’t know if that is what the “unexpected location creo” message is referring to.

Hi Javier,

To use the tool, it’s best to use master branch, because the other things you mentioned are not up-to-date. To build a docker image from master, build it in standard way using the Dockerfile file that’s provided in the root.

“creo” in your error refers to CREODIAS, which the tool doesn’t support. It supports only AWS cloud.

Hi @tslijepcevic,

Thanks for the reply. I thought the way to go was rebuilding, but was hoping to avoid it.

From what you say, then, even using master branch I would not be able to make it work because I am using CREODIAS buckets. Is that correct?

Regards

That’s correct. CREODIAS buckets are not supported.

Thanks, I’ll keep using my own scripts then