Expose port 5000 on the dockerfile
Nobody has claimed this yet.
- Dominant language
- C#
- Stars
- 5.1k
- Forks
- 1.6k
- PR merge metrics
- No merged PRs in 30d
Description
Is your feature request related to a problem? Please describe.
When I try to create a container based on the image immybot/remotely I cannot create a reverse proxy page based on the port 5000 on synology because the container image does not expose the port by default.
Describe the solution you'd like
Add a line to immybot/remotely to expose TCP port 5000
Describe alternatives you've considered
I have to create a mapping to the port on the container to the host and do the reverse proxy from there. It is not an ideal situation.
Additional cooments
I don't understand why port 8080 is exposed when it doesn't seem to be necessary.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Open the repository Dockerfile and inspect its existing EXPOSE entries, including port 8080. Add the requested TCP port 5000 exposure, then verify that the built image metadata reports the port.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 55/100