Docker run jitsi/prosody failed as 5222/5069/5347 ports are in used

I tried to use docker run to start a jitsi/prosody container, but failed. Here is the command:
docker run -it -v /opt/prosody/conf.avail/jitsi.pangu.com.cfg.lua:/config/prosody.cfg.lua jitsi/prosody

the logs read:
Status: Downloaded newer image for jitsi/prosody:latest
[s6-init] making user provided files available at /var/run/s6/etc…exited 0.
[s6-init] ensuring user provided files have correct perms…exited 0.
[fix-attrs.d] applying ownership & permissions fixes…
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts…
[cont-init.d] 01-set-timezone: executing…
[cont-init.d] 01-set-timezone: exited 0.
[cont-init.d] 10-config: executing…
Adding user prosody' to groupsasl’ …
Adding user prosody to group sasl
Done.
You need to supply at least one hostname
Usage: /usr/bin/prosodyctl cert generate HOSTNAME [HOSTNAME+]
Generates a self-signed certificate for the current hostname(s)
You need to supply at least one hostname
Usage: /usr/bin/prosodyctl cert generate HOSTNAME [HOSTNAME+]
Generates a self-signed certificate for the current hostname(s)
mv: cannot stat ‘/config/data/.crt’: No such file or directory
mv: cannot stat '/config/data/
.key’: No such file or directory
[cont-init.d] 10-config: exited 0.
[cont-init.d] done.
[services.d] starting services
saslauthd[229] :num_procs : 5
saslauthd[229] :mech_option: /etc/saslauthd.conf
saslauthd[229] :run_path : /var/run/saslauthd
saslauthd[229] :auth_mech : ldap
saslauthd[229] :mmaped shared memory segment on file: /var/run/saslauthd/cache.mmap
saslauthd[229] :bucket size: 96 bytes
saslauthd[229] :stats size : 36 bytes
saslauthd[229] :timeout : 28800 seconds
saslauthd[229] :cache table: 985828 total bytes
saslauthd[229] :cache table: 1711 slots
saslauthd[229] :cache table: 10266 buckets
saslauthd[229] :flock file opened at /var/run/saslauthd/cache.flock
saslauthd[229] :using accept lock file: /var/run/saslauthd/mux.accept
saslauthd[229] :master pid is: 0
saslauthd[229] :listening on socket: /var/run/saslauthd/mux
saslauthd[229] :using process model
saslauthd[229] :forked child: 235
saslauthd[229] :forked child: 236
saslauthd[229] :forked child: 237
saslauthd[229] :forked child: 238
saslauthd[229] :acquired accept lock
[services.d] done.
startup info Hello and welcome to Prosody version 0.11.2
startup info Prosody is using the select backend for connection handling
portmanager info Activated service ‘s2s’ on []:5269, [::]:5269
mod_posix info Prosody is about to detach from the console, disabling further console output
startup info Hello and welcome to Prosody version 0.11.2
startup info Prosody is using the select backend for connection handling
socket warn server.lua, [::]:5269: address already in use
portmanager error Failed to open server port 5269 on ::, check that Prosody or another XMPP server is not already running and using this port
socket warn server.lua, [
]:5269: address already in use
portmanager error Failed to open server port 5269 on , check that Prosody or another XMPP server is not already running and using this port
portmanager info Activated service ‘s2s’ on no ports
mod_s2s warn s2s not listening on any ports, outgoing connections may fail
socket warn server.lua, [::]:5222: address already in use
portmanager error Failed to open server port 5222 on ::, check that Prosody or another XMPP server is not already running and using this port
socket warn server.lua, [
]:5222: address already in use
portmanager error Failed to open server port 5222 on , check that Prosody or another XMPP server is not already running and using this port
portmanager info Activated service ‘c2s’ on no ports
portmanager info Activated service ‘legacy_ssl’ on no ports
mod_posix info Prosody is about to detach from the console, disabling further console output
startup info Hello and welcome to Prosody version 0.11.2
startup info Prosody is using the select backend for connection handling
socket warn server.lua, [::]:5222: address already in use
portmanager error Failed to open server port 5222 on ::, check that Prosody or another XMPP server is not already running and using this port
socket warn server.lua, [
]:5222: address already in use
portmanager error Failed to open server port 5222 on , check that Prosody or another XMPP server is not already running and using this port
portmanager info Activated service ‘c2s’ on no ports
portmanager info Activated service ‘legacy_ssl’ on no ports
socket warn server.lua, [::]:5280: address already in use
portmanager error Failed to open server port 5280 on ::, check that Prosody or a BOSH connection manager is not already running
socket warn server.lua, [
]:5280: address already in use
portmanager error Failed to open server port 5280 on , check that Prosody or a BOSH connection manager is not already running
portmanager info Activated service ‘http’ on no ports
portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
portmanager info Activated service ‘https’ on no ports
mod_http warn Not listening on any ports, ‘bosh’ will be unreachable
mod_posix info Prosody is about to detach from the console, disabling further console output
startup info Hello and welcome to Prosody version 0.11.2
startup info Prosody is using the select backend for connection handling
socket warn server.lua, [
]:5269: address already in use
portmanager error Failed to open server port 5269 on , check that Prosody or another XMPP server is not already running and using this port
socket warn server.lua, [::]:5269: address already in use
portmanager error Failed to open server port 5269 on ::, check that Prosody or another XMPP server is not already running and using this port
portmanager info Activated service ‘s2s’ on no ports
mod_s2s warn s2s not listening on any ports, outgoing connections may fail
socket warn server.lua, [
]:5280: address already in use
portmanager error Failed to open server port 5280 on *, check that Prosody or a BOSH connection manager is not already running
socket warn server.lua, [::]:5280: address already in use
portmanager error Failed to open server port 5280 on ::, check that Prosody or a BOSH connection manager is not already running
portmanager info Activated service ‘http’ on no ports
portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
portmanager error Error binding encrypted port for https: No certificate present in SSL/TLS configuration for https port 5281
portmanager info Activated service ‘https’ on no ports

Please help me to know how to run jitsi/prosody container successfully. Thanks!

Do you have another prosody instance running on your server?

resolved, thanks