question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

"Invalid argument - repository path is not a valid directory" when running local S3 on port 80

See original GitHub issue

Description I’m trying to pull models from a local S3 using --model-repository=s3://cool.url.com:80/bucket_name/path/to/repo as described here but it gives the following error:

error: creating server: Invalid argument - repository path is not a valid directory

Changing the port from 80 to anything else gives access error, which makes sense

error: creating server: Internal - Could not get MetaData for bucket with name <bucket_name>

Removing 80 and using --model-repository=s3://cool.url.com/bucket_name/path/to/repo makes Triton think that the url is the bucket name:

error: creating server: Internal - Could not get MetaData for bucket with name cool.url.com

Triton Information What version of Triton are you using? nvcr.io/nvidia/tritonserver:20.08-py3

Are you using the Triton container or did you build it yourself? I pulled the image

To Reproduce Steps to reproduce the behavior. Get a local S3 running on port 80 Add your models pull them from there following here

Describe the models (framework, inputs, outputs), ideally include the model configuration file (if using an ensemble include the model configuration file for that as well). No relevant

Expected behavior I expect models to be loaded into Triton.

Issue Analytics

  • State:closed
  • Created 3 years ago
  • Comments:10 (4 by maintainers)

github_iconTop GitHub Comments

1reaction
CoderHamcommented, Oct 27, 2020

Thank you for bringing this to our attention. Could you repeat these steps to confirm it is not a configuration issue on your end?

  1. Use S3 command line to confirm the credentials are set correctly.
  2. Confirm that the path is a folder and not a file.
  3. Use Tritonserver 20.10/20.09
  4. Ensure you are following the S3 bucket name conventions.
0reactions
deadeyegoodwincommented, Jan 26, 2021

Closing, please reopen if still an issue.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Troubleshoot endpoint URL connection error ... - Amazon AWS
To troubleshoot this error, check the following: Confirm that you're using the correct AWS Region and Amazon S3 endpoint.
Read more >
Troubleshoot endpoint URL connection error in Amazon S3
I'm trying to run the cp or sync command on my Amazon Simple Storage Service (Amazon S3) bucket. However, I'm getting the "Could...
Read more >
S3 API Requests must be made to API port - Stack Overflow
The error message indicates that you need to use the API port instead of console port while using mc. /usr/bin/mc config host add...
Read more >
Dockerfile reference - Docker Documentation
The instruction is not case-sensitive. However, convention is for them to be UPPERCASE to distinguish them from arguments more easily. Docker runs instructions ......
Read more >
Troubleshooting Omnibus GitLab installation issues
This error is thrown when /etc/gitlab/gitlab.rb configuration file contains configuration that is invalid or unsupported. Double check that there are no ...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found