Hi,

the warning is just that: it's a warning. You can solve it by setting the 
servername in the apache configuration just as mentioned in the warning.

You did not really describe what your actual problem is - but I guess your 
container exits/stops right after the warning? Is that correct? In that case, 
as mentioned above, the warning is just a coincidence, it is not causing the 
container to stop. I'd check for other reasons why the container stops working.

As a side node: the images from @jenserat are built via packages supplied by 
inverse, the company behind sogo. Inverse stopped providing these packages, so 
you might consider using another container image or building one on your own.

Cheers,

Roland

Am Montag, Juni 12, 2017 14:01 CEST, "Catarina Loureiro" 
(catarinaloureir...@gmail.com) <users@sogo.nu> schrieb:
 Hey! Im sorry for late answer, but i started a new thing and i let this going 
behind... So, i use this one: https://hub.docker.com/r/jenserat/sogo/    and 
there you have like commands that you should do, but when i do, i keep 
recieving this: AH00558: apache2: Could not reliably determine the server's 
fully qualified domain name, using 172.17.0.2. Set the 'ServerName' directive 
globally to suppress this message Already made a network bridge for docker and 
then it appears like this: AH00558: apache2: Could not reliably determine the 
server's fully qualified domain name, using 172.17.0.3. Set the 'ServerName' 
directive globally to suppress this message. And everytime i create another 
one, keeps going 4.5.6.7 on the last number for that IP.  2017-05-04 6:03 
GMT+01:00 "Roland Wolters" <users@sogo.nu>:Hi Catarina,

I am not used to the Docker image from JensErat, however that does not look 
tooo sophisiticated. So how about you shortly describe what commands you 
actually tried, and what the output was? That would give us a chance to 
actually look at the error you are facing and if we might be able to help you.

Cheers,

Roland

Am Mittwoch, Mai 03, 2017 16:33 CEST, "Catarina Loureiro" 
(catarinaloureir...@gmail.com) <users@sogo.nu> schrieb:
 Hey.  Sorry, didnt saw any answer i thought it was about no title. Was exactly 
that one from JensErat that i pulled.But i cant figure out how to put that 
work. Im not fully familiar with docker, but im doing with docker because my 
coordinator asked me to.. Thanks.  Em 03/05/2017 3:06 da tarde, "Marc 
Patermann" <users@sogo.nu> escreveu:Catarina,

you already posted this last week. :)

Am 03.05.2017 um 14:31 Uhr schrieb Catarina Loureiro 
(catarinaloureir...@gmail.com):Hey, i would appreciate if you could help me.

Im in my internship and this is a company that they have their own
system operative in Debian Wheezy 7.7. I installed already docker, i
already pull the image but now i cant put this work. Why exactly did you do 
that (docker)?
Are you familiar with docker in general?
What image did you pull? Were there instructions? Like here:
https://github.com/JensErat/docker-sogo (first google hit)
 I would like to know how i should procede and if you could help me
implement this new groupware on the company. There is the ZEG VM image: 
https://sogo.nu/download.html#/zeg

You could use the "Package-based Installation Helper" on 
https://sogo.nu/download.html and install the nightlies. Follow the 
instructions of the "SOGo - Installation and Configuration Guide" 
https://sogo.nu/support/index.html#/documentation.

Marc
--
users@sogo.nu
https://inverse.ca/sogo/lists--
users@sogo.nu
https://inverse.ca/sogo/lists


--
Roland Wolters
mobile: +49 173 294 678 6
e-mail: r...@bayz.de
blog: https://liquidat.wordpress.com
twitter: @liquidat
jabber: liqui...@jabber.de --
users@sogo.nu
https://inverse.ca/sogo/lists--
users@sogo.nu
https://inverse.ca/sogo/lists


--
Roland Wolters
mobile: +49 173 294 678 6
e-mail: r...@bayz.de
blog: https://liquidat.wordpress.com
twitter: @liquidat
jabber: liqui...@jabber.de
-- 
users@sogo.nu
https://inverse.ca/sogo/lists

Reply via email to