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

+2 votes

Hi Guys,

I am trying to launch one httpd container, but It shows me the below error.

$ docker run -it --name web1 httpd:latest
AH00558: httpd: 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 AH00558: httpd: 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 [Mon May 04 19:31:24.452104 2020] [mpm_event:notice] [pid 1:tid 140087193076864] AH00489: Apache/2.4.43 (Unix) configured -- resuming normal operations [Mon May 04 19:31:24.452376 2020] [core:notice] [pid 1:tid 140087193076864] AH00094: Command line: 'httpd -D FOREGROUND' [Mon May 04 19:31:24.512748 2020] [mpm_event:notice] [pid 1:tid 140087193076864] AH00492: caught SIGWINCH, shutting down gracefully

How can I solve this error?

May 5 in Docker by akhtar
• 25,050 points
1,305 views

1 answer to this question.

0 votes

Hi@akhtar,

In your command use -d, it will detach your container in background. You can not login in a running process. So use the below given command.

$ docker run -it -d --name web httpd:latest

Hope this will help.

answered May 5 by MD
• 56,520 points

Related Questions In Docker

0 votes
1 answer
0 votes
1 answer

Docker image of maven returns this error - could not create local repository

Instead of mounting the root/.m2 folder to ...READ MORE

answered Aug 10, 2018 in Docker by Sophie may
• 10,100 points
1,023 views
+3 votes
3 answers

Not able to connect worker nodes to the swarm. Connection refused error

This definitely has to be a firewall issue. ...READ MORE

answered Apr 26, 2019 in Docker by Vaidya
9,046 views
+2 votes
1 answer
+2 votes
1 answer

Deploy Docker Containers from Docker Cloud

To solve this problem, I followed advice ...READ MORE

answered Sep 3, 2018 in AWS by Priyaj
• 57,640 points
777 views
0 votes
1 answer

could not initialize port layer: bridge mask is not compatible with bridge pool mask

Hi@akhtar, You may specified a --bridge-network-range that cannot accommodate a ...READ MORE

answered Apr 8 in Docker by MD
• 56,520 points
44 views