-
-
Notifications
You must be signed in to change notification settings - Fork 2.6k
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
Official 🐋 Docker image #4088
Labels
Comments
Please. This could lead to a much more straightforward setup for development. |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Feature Description
As mentioned earlier, people are creating many
Dockerfile
s and container images. This leads to different setups, versions, bugs (i.e. 4040, 3560, 3281) and probably untrustworthy container images on Docker hub.Furthermore bugs like #4040/22775 would appear much earlier if a container would be build and tested in a CI workflow or so. Therefore there's a chance that they could be fixed earlier.
So it probably would make sense to have an official and properly versioned container on Docker hub.
PS: Having a supported and working image would probably also avoid people intentionally using outdated versions.
PPS: Also a more secure setup could be ensured (i.e. not running the image with
root
user)The text was updated successfully, but these errors were encountered: