Restarting Containers

[Oratorian]

I am using the dev branch for some testing and the Containers TAB gives the ability to restart all containers.

But it is not, It is simply just throwing Error: when i click the restart behind a container. This also happens when trying to restart SoGo

Attached some screenshots

[andryyy]

Probably an older dockerapi container. That’s dev.

Mit besten Grüßen André Peters

Am 18.12.2017 um 15:38 schrieb Oratorian notifications@github.com:

I am using the dev branch and the Containers TAB gives the ability to restart all containers.

But it is not, It is simply just throwing Error: when i click the restart behind a container. This also happens when trying to restart SoGo

Attached some screenshots

— You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[Oratorian]

Does the actual master branch include the quarantine and the debugging Menu option?

Or any way to get around this olderapi thing?

[andryyy]

No it doesn’t. Try docker-compose build dockerapi-mailcow followed by up -d

Mit besten Grüßen André Peters

Am 18.12.2017 um 15:53 schrieb Oratorian notifications@github.com:

Does the actual master branch include the quarantine and the debugging Menu option?

Or any way to get around this olderapi thing?

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[Oratorian]

I recompiled the dockerapi-mailcow

I attached then to the dockerapi to get the logs

`Attaching to mailcowdockerized_dockerapi-mailcow_1 dockerapi-mailcow_1 | Exception in thread Thread-1: dockerapi-mailcow_1 | Traceback (most recent call last): dockerapi-mailcow_1 | File "/usr/local/lib/python2.7/threading.py", line 801, in bootstrap_inner dockerapi-mailcow_1 | self.run() dockerapi-mailcow_1 | File "/usr/local/lib/python2.7/threading.py", line 754, in run dockerapi-mailcow_1 | self.target(*self.args, **self.kwargs) dockerapi-mailcow_1 | File "/server.py", line 113, in startFlaskAPI dockerapi-mailcow_1 | app.run(debug=False, host='0.0.0.0', port='8080', threaded=True) dockerapi-mailcow_1 | File "/usr/local/lib/python2.7/site-packages/flask/app.py", line 841, in run dockerapi-mailcow_1 | run_simple(host, port, self, **options) dockerapi-mailcow_1 | File "/usr/local/lib/python2.7/site-packages/werkzeug/serving.py", line 733, in run_simple dockerapi-mailcow_1 | raise TypeError('port must be an integer') dockerapi-mailcow_1 | TypeError: port must be an integer dockerapi-mailcow_1 |

[andryyy]

Make Port an integer. This is dev and not expected to work. Other stuff is likely not working, too. It is a branch you can work on and fix stuff.

Am 18.12.2017 um 16:17 schrieb Oratorian notifications@github.com:

I recompiled the dockerapi-mailcow

I attached then to the dockerapi to get the logs

Attaching to mailcowdockerized_dockerapi-mailcow_1 dockerapi-mailcow_1 | Exception in thread Thread-1: dockerapi-mailcow_1 | Traceback (most recent call last): dockerapi-mailcow_1 | File "/usr/local/lib/python2.7/threading.py", line 801, in bootstrap_inner dockerapi-mailcow_1 | self.run() dockerapi-mailcow_1 | File "/usr/local/lib/python2.7/threading.py", line 754, in run dockerapi-mailcow_1 | self.target(*self.args, **self.kwargs) dockerapi-mailcow_1 | File "/server.py", line 113, in startFlaskAPI dockerapi-mailcow_1 | app.run(debug=False, host='0.0.0.0', port='8080', threaded=True) dockerapi-mailcow_1 | File "/usr/local/lib/python2.7/site-packages/flask/app.py", line 841, in run dockerapi-mailcow_1 | run_simple(host, port, self, **options) dockerapi-mailcow_1 | File "/usr/local/lib/python2.7/site-packages/werkzeug/serving.py", line 733, in run_simple dockerapi-mailcow_1 | raise TypeError('port must be an integer') dockerapi-mailcow_1 | TypeError: port must be an integer dockerapi-mailcow_1 | root@mx:~/mailcow-dockerized#

— You are receiving this because you commented. Reply to this email directly, view it on GitHub, or mute the thread.

[bkleiner]

It's maybe worth mentioning that the master branch showed the same problem for me starting with a fresh install.

[andryyy]

I guess that happened when you built the images yourself. The pushed images work fine in master.

[bkleiner]

Yep, you right, i just checked again, it only happens when you build yourself.