-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Why does docker-compose up-d report errors pull access denied for sentry-cleanup-self-hosted-local, repository does not exist or may require 'docker login': denied: requested access to the resource i…?? #3036
Comments
Assigning to @getsentry/support for routing ⏲️ |
version 24.4.2 |
|
Hello, a few questions:
|
I executed it in the following order |
I am from China, similar to this configuration BASE_IMAGE recognition seems to have a problem, the default pull vroom-cleanup-self-hosted-local, but in fact docker.hub does not have this mirroring, so directly reported pull access is rejected, vroom-cleanup-self-hosted-local, the repository does not exist or may need'docker login ': Rejected: The requested resource is, and I am sure to execute docker pull getsentry/vroom: 24.4.2 can pull successfully, I did not open the proxy |
Yes, some of the containers should be built by the |
My/etc/docker/daemon.json only has the following content, and no docker proxy is configured |
I seem to have solved this problem. My local environment umask is 027, which causes the directory permissions of my git clone code file to be incorrect. I feel your reply |
So.. did the installation process finished successfully? |
The test host was successful, and I am ready to try it in production. |
We are also facing this issue. We are running Sentry on Elastic Beanstalk, and the thing is we cannot configure much of the behaviour of the Docker platform. Even if I use |
@ngudbhav I don't think that's something we can help either. The self-hosted sentry is aimed for a plain old VM with regular Docker installed. |
Duplicate of #2641 (I am also facing the issue) The script with pulling the images almost worked:
Then I executed install.sh, then
|
I got this error a while ago on a Debian 12 server while migrating from 24.4.2 to 24.5.0. What I did was:
I don't know what caused this, but probably this is a Docker issue, not a specific self-hosted issue. *PS. My Docker is not rootless, so I need to use |
Environment
SaaS (https://sentry.io/)
What are you trying to accomplish?
Normal download image installation
How are you getting stuck?
Where in the product are you?
Unknown
Link
No response
DSN
No response
Version
No response
The text was updated successfully, but these errors were encountered: