Hi, I can see those values correctly with the doveconf -nc command. Here is
the part of output:
bash-4.2# doveconf -nc /etc/dovecot/director.conf
# 2.2.36 (1f10bfa63): /etc/dovecot/director.conf
# OS: Linux 4.1.12-112.14.11.el7uek.x86_64 x86_64 Red Hat Enterprise Linux
Server release 7.7 (Maipo)
#
I have noticed several issues with dovecot, trying to run it without
root. Which is preferable in any container environment. Maybe you would
like me to document these somewhere? So at some point they can be
applied.
-Original Message-
From: Naveen Reddy [mailto:naveenredd...@gmail.co
If you are running your container as root. You will not have the issues
I encountered. Dovecot is dropping to the 'dovecot' and 'dovenull'(?)
when needed, this is fine.
PS. I would not recommend using internal logging, use something like
this to log to the host or remote syslog.
docker run -v
Hi Marc,
I can see the processes are running as a root in container environment. Do
you think that still have issues ?
Here is the processes running inside container:
bash-4.2# ps -ef
UIDPID PPID C STIME TTY TIME CMD
root 1 0 0 Dec27 ?00:00:00 /bin/bash /bo
Maybe start over with your configuration. Start with default setup, see
if everything is running and then start changing the configuration step
by step, see when it goes wrong. I saw you have some ldap configs, maybe
outside communication fails, acls? sff level?
I saw you were using this el7.
I'm not using internal logging. I'm running the docker with the logging to
the host.
I have used the same options you have specified.
The problem is that the below processes are not running inside docker
container whereas the standalone dovecot is running these processes(meaning
without container)
You could also try our docker images, see
https://hub.docker.com/u/dovecot
Aki
On 30/12/2019 12:18 Naveen Reddy wrote:
I'm not using internal logging. I'm running the docker with the logging to the host.
Aki, This image doesn't have a director service, just the dovecot is
running.
Marc, I'm running the docker container in a privileged mode and it doesn't
seem to have any issues reaching out to the outside network. I will try
running with default config and see what fails.
Thanks & Regards,
Navee
On 30/12/2019 14:20 Naveen Reddy wrote:
Aki, This image doesn't have a director service, just the dovecot is running.
This would be because you did not configure it. As the description says, you need to mount /
Dear all,
I have recently migrated from my old Debian 8 (jessie) system to a new VM with
fresh Debian 10 (buster) installation.
Previous dovecot version was 2.2.13 and now I have 2.3.4.1.
Dovecot was setup from Debian packages.
Mostly, it is working, but one problem is just frustrating me.
The nu
Hi all
I'm facing an issue while running dovecot inside a singularity
(https://sylabs.io/singularity/) container
dovecot version is 2.3.4.1 (configuration below) running on debian
buster, inside a container made with singularity version 3.4.2
unfortunately, when I try to start dovecot, it gives:
11 matches
Mail list logo
