Skip to content
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

When I use an image with the tag latest-alpine, the container unexpectedly occupies port 443 for https #659

Open
blueberry-pie-11 opened this issue Sep 2, 2024 · 2 comments
Assignees
Labels
Docker fixed but not released Issue is fixed in some branch or commit but not yet in main branch

Comments

@blueberry-pie-11
Copy link

Description

If you use the WEBPORT variable to set a specific port (such as 5000), the container will normally provide an http interface on port 5000, but will additionally occupy port 443 for https services.
When docker uses the host network mode, if nginx is used as a reverse proxy (https), it will cause a conflict with nginx's port 443, and eventually it will be stuck in a continuous restart.

@blueberry-pie-11
Copy link
Author

This is because the latest-alpine image is built with apache2-ssl installed, which I recommend removing. Users should set up their own reverse proxy (e.g., nginx) to implement https, not librespeed. At the same time, I don't think it will be easy to use librespeed's https function.

@sstidl
Copy link
Collaborator

sstidl commented Oct 26, 2024

removed apache2-ssl dependency. will be release with #678

@sstidl sstidl self-assigned this Oct 26, 2024
@sstidl sstidl added Docker fixed but not released Issue is fixed in some branch or commit but not yet in main branch labels Oct 26, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Docker fixed but not released Issue is fixed in some branch or commit but not yet in main branch
Projects
None yet
Development

No branches or pull requests

2 participants