-
-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Project setup > failed to solve: sentry-self-hosted-local: pull access denied #3476
Comments
@bobvandevijver please do not trim the reproduction steps. Currently what you shared is not enough to reproduce the issue.
This warning indicates that your |
@BYK I'm not sure which step you are missing, except for the These are the literal steps, running as root on a fresh Debian installation, that ensures you will get the error.
Removing the local builder image resolves the issues and lets the
(I removed the v6 networking in case you do not have docker configured for that.) |
@bobvandevijver ah, sorry I misread some stuff here. So here's what's going on: The I don't know what we can do about this as we don't use the setup you are describing. If the information above gives you a hint to fix it, we are open to pull requests though. |
Self-Hosted Version
24.12.0
CPU Architecture
x86_64
Docker Version
27.3.1
Docker Compose Version
2.29.7
Machine Specification
Steps to Reproduce
I'm resubmitting #2641 as I believe I have a reproducer, even though I am not absolutely sure it is related or even a sentry issue.
We are in the process of disabling the default
bridge
network to force all containers to have a dedicated network, and for that reason we needed to create a local builder on a dedicatedbuild
network.Docker compose automatically uses this container for its builds, but the sentry install procedure seems to have issues resolving a local image.
I tried changing
dbuild
todocker buildx build $proxy_args
ininstall/dc-detect-version.sh
, but that did not solve the issue.Expected Result
I expect to be able to get sentry running, even with the custom local builder.
Actual Result
Event ID
No response
The text was updated successfully, but these errors were encountered: