Comments (5)
Thanks for the poke over on official-images. Sorry for the slow reply here and for not getting back to #208. 🙇♂️
Elasticsearch, Logstash, and Kibana were the result of extensive discussion and ongoing collaboration with Elastic Inc. and is very unlikely to be repeated.
We'd love to find a way that Sentry images could continue to be published in the official-images program.
Since every change of every image is reviewed by humans, we cannot reasonably review the hourly cadence I see on tags pushed to getsentry/sentry
. We do not allow nightly builds and instead recommend weekly at most (see also docker-library/julia#25 (comment) and docker-library/php#991).
On a related note, the Sentry official-image Hub page is currently complicated by the Docker Store "publisher image" masking the Docker Hub official-image listing similar to Aerospike. I am uncertain how this affects docker pull
.
from docker-sentry.
Hi @yosifkit and no worries about the late turn-over, I figured you folks are busy and wasn't sure you were getting notified about external mentions, hence the issue over the official repo 🙂
Since every change of every image is reviewed by humans, we cannot reasonably review the hourly cadence I see on tags pushed to getsentry/sentry. We do not allow nightly builds and instead recommend weekly at most (see also docker-library/julia#25 (comment) and docker-library/php#991).
Yes, I definitely agree and the reason I'm bringing this up is because we are planning to switching to CalVer (while keeping the nightlies, but not for the Docker Library image) with a monthly cadence (except for urgent hot fixes). I think this would be a much more manageable load on your side, right?
Elasticsearch, Logstash, and Kibana were the result of extensive discussion and ongoing collaboration with Elastic Inc. and is very unlikely to be repeated.
I understand this but keeping a separate image and build process, just for the Docker Library is not feasible for us. Our current Docker setup is likely to evolve with more build targets (build base, runtime base, development etc.).
The closest we can get I think might be us having a base sentry-runtime
image, and then pulling the latest pip wheel into that image but I'd much rather not depend on pip as packing that wheel is also not guaranteed to survive (as our PyPI demand is pretty low after Docker, so yay? 🎉 ).
I'm also open to making our images be more reproducible/consistent with some input from you. I understand that anything that pulls things from apt
or likes, even with pinned versions may change in time so I don't really know what else we can do.
On a related note, the Sentry official-image Hub page is currently complicated by the Docker Store "publisher image" masking the Docker Hub official-image listing similar to Aerospike. I am uncertain how this affects docker pull.
I don't know much about this but I don't think we are interested in a Store functionality (I think that explains the $0 thing on that page). Do you know if this can be disabled? Is it us enabling this somehow?
from docker-sentry.
@yosifkit ping :)
from docker-sentry.
@yosifkit we've published the first of many monthly CalVer releases: https://github.com/getsentry/sentry/releases/20.6.0
LMK when is a good time to finalize this discussion.
from docker-sentry.
Closing this and archiving the repo as we decided to remove the image in favor of the full onpremise package
from docker-sentry.
Related Issues (20)
- release 9.1.1-onbuild?
- upload-sourcemaps failed - [uwsgi-body-read] Timeout reading 65536 bytes. Content-Length: x consumed: 0 left: x` HOT 2
- Cannot find Client Keys in project HOT 1
- Possibility to run as non-root user HOT 22
- Incorrect default SMTP user/password HOT 5
- Please sign newer docker images HOT 11
- Docs not built HOT 1
- Track sentry errors with itself HOT 2
- registration email missing domain HOT 3
- Upgrade to Buster base image HOT 1
- 404 Error with event committers HOT 3
- "No module named google.cloud.storage.client" HOT 4
- No default org created HOT 1
- Error response from daemon: Cannot restart container 5b40898f7f44: failed to listen to abstract unix socket "/containerd-shim/moby/5b40898f7f442d78153d920f1e457252514114760b7dbd3f23011a2261e81ded/shim.sock": listen unix /containerd-shim/moby/5b40898f7f442d78153d920f1e457252514114760b7dbd3f23011a2261e81ded/shim.sock: bind: address already in use: unknown HOT 1
- docker build of 9.1 fails with gpg HOT 3
- Get Sentry image running on AWS ECS HOT 2
- Sentry 10 support HOT 2
- Enhnace Dockerfile to automatically load and "install" plugins HOT 4
- sentry 10 image not available in docker hub HOT 3
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from docker-sentry.