[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
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

Update Dockerfile so it doesn't automatically bind any TCP listeners #1942

Merged
merged 2 commits into from
Dec 6, 2024

Conversation

mmahdium
Copy link
Contributor
@mmahdium mmahdium commented Nov 13, 2024

Made changes so it doesn't automatically bind any TCP listener to prevent nanomq.conf TCP listener from being overwritten.
It is having problems whenever I provide my nanomq.conf file that has a TCP listener with a different port, It only binds to default 1883 and not my conf file.

Output from 'top' in the docker container:
image

my nanomq.conf file:

mqtt {
    retry_interval = 10s
    keepalive_multiplier = 1.25
}

listeners.tcp {
    bind = "0.0.0.0:444"
}

Docker command used to run the container:

docker run  -p 444:444 -p 1883:1883 -d  -v /root/nanomqDockerCompose/nanomq.conf:/etc/nanomq.conf -v /root/nanomqDockerCompose/nanomq_pwd.conf:/etc/nanomq_pwd.conf --name nanomq emqx/nanomq

It only binds to 1883 as provided in

CMD ["--url", "nmq-tcp://0.0.0.0:1883"]

But in other variants of the image (slim,dev,full) it is different for some reason:

CMD ["--conf", "/etc/nanomq.conf"]

Made changes so it doesn't automatically bind any TCP listener to prevent nanomq.conf TCP listener from being overwritten
@JaylinYu
Copy link
Member

In Principle, I agree.
What says you @Rory-Z

@JaylinYu JaylinYu merged commit 706e22b into nanomq:master Dec 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants