I'm trying to bring up a container using following Dockerfile.
But ends in error.

[Dockerfile]
FROM ubuntu:15.04

RUN apt-get update && apt-get install -y iputils-ping apache2

ENV var1=Nigel var2=Poulton

ENTRYPOINT ["apache2ctl"]

----------------------------------------------------------

[root@puppetmaster hw]# docker run -it nigel1 /bin/bash
/usr/sbin/apache2ctl: 87: ulimit: error setting limit (Operation not permitted)
Setting ulimit failed. See README.Debian for more information.
Usage: /usr/sbin/apache2 [-D name] [-d directory] [-f file]
[-C "directive"] [-c "directive"]
[-k start|restart|graceful|graceful-stop|stop]
[-v] [-V] [-h] [-l] [-L] [-t] [-T] [-S] [-X]
Options:
-D name : define a name for use in <IfDefine name> directives
-d directory : specify an alternate initial ServerRoot
-f file : specify an alternate ServerConfigFile
-C "directive" : process directive before reading config files
-c "directive" : process directive after reading config files
-e level : show startup errors of level (see LogLevel)
-E file : log startup errors to file
-v : show version number
-V : show compile settings
-h : list available command line options (this page)
-l : list compiled in modules
-L : list available configuration directives
-t -D DUMP_VHOSTS : show parsed vhost settings
-t -D DUMP_RUN_CFG : show parsed run settings
-S : a synonym for -t -D DUMP_VHOSTS -D DUMP_RUN_CFG
-t -D DUMP_MODULES : show all loaded modules
-M : a synonym for -t -D DUMP_MODULES
-t : run syntax check for config files
-T : start without DocumentRoot(s) check
-X : debug mode (only one worker, do not detach)
[root@puppetmaster hw]#

Well, you made the Dockerfile, and then tried to run it.
Did you try and build it first? That's what Dockerfiles are for
Otherwise,
shows what?

What's the source of this Dockerfile, originally?

Yep, I forgot to put the part where I built from the Dockerfile. I think I ran something like "docker build t="nigel1"

I'll run "docker images nigel*" when I get home.

The Dockerfile is from PluralSight's Docker course.

Are you familiar with the error?

Thanks.

Post the Dockerfile when you get home.
I don't believe the "FROM ubuntu:15.04" in it is correct.
And there may be some other stuff missing from your post.
I checked PluralSite but was unwilling to sign up.
Apache is dead easy on Docker.
I did a pull of ubuntu's official image and I only get
DISTRIB_DESCRIPTION="Ubuntu 14.04.2 LTS"

You post the Dockerfile and I can troubleshoot it further.

Thanks for your time.

I just checked the pluralsight course module again and that Dockerfile I posted in original post is correct.

I've had other Dockerfile(s) that included "FROM ubuntu:15.04" and they worked fine.

It's just the apache part that's having trouble.

Hmm.. but I'm curious what "docker images nigel1" will yield.

Thanks again and please see my update later.

No worries.

Subscribed with interest...

Thanks.

haha, actually I just re-produced the problem at work. But this one includes a proxy.
I did some web search and seems "FROM ubuntu:15.04" syntax is correct.
Here's the updated Dockerfile and "docker image" output.

--------------------------------
FROM ubuntu:15.04

ENV http_proxy <http://www-proxy.work.com:80>
ENV https_proxy <http://www-proxy.work.com:80>

RUN apt-get update && apt-get install -y iputils-ping apache2

ENV var1=Nigel var2=Poulton

ENTRYPOINT ["apache2ctl"]

--------------------------------

[root@puppetmaster hw]# docker images
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
nigel1 latest 6c99781406e3 4 minutes ago 243.4 MB
ubuntu 15.04 bd94ae587483 3 weeks ago 131.3 MB
[root@puppetmaster hw]# docker images nigel1
REPOSITORY TAG IMAGE ID CREATED VIRTUAL SIZE
nigel1 latest 6c99781406e3 5 minutes ago 243.4 MB
[root@puppetmaster hw]#


Thanks again for your time.

installing 15.04 Desktop now.
I'll update my results...

OK.
I told you there was stuff missing

vm.local:

Built is using
ran it:
Verified it's running:
Verified the docker logs for the container:
spits out
AH00558: apache2: Could not reliably determine the server's fully qualified domain name, using 172.17.0.12. Set the 'ServerName' directive globally to suppress this message

a non-fatal error and easily correctable.
That's all I have, for now.

Is the purpose of this course you taking, has the theme of the current instruction center around debugging?
Because without an EXPOSE directive to open the port, it was doomed to fail.

Also
apache2ctl has to run in the foreground for the container to have a writable state.
and to serve up the default /var/www/html/index.html in the container.

1 members found this post helpful.

Course is called "Docker Deep Dive" and in "Diving Deeper with Dockerfile" module and in "ENV Instruction" lesson.

I modified the Dockerfile with EXPOSE and your ENTRYPOINT. It's somewhat running without "/bin/bash"

Are you running all this on a Ubuntu or CentOS server? Can it cause trouble if I try to run Ubuntu Docker image on a CentOS server?

I'll bring this up with the author.

Thanks a lot for your time and effort to try and solve this.

I'll probably post more as I run into troubles. Please continue to stalk me and posts. (might even update this one).

(You must be very smart and also popular at wherever you work).

Ubuntu 15.04/vivid Desktop 64 bit Virtualbox guest.
No worries. It's sorta mostly basic stuff and that's all I know atm, the basics.

What I don't know could fill a warehouse,
What I do know could fill an outhouse.

Not that smart. I make plenty of mistakes, believe you me.
The key is fixing more than I break.

If you get in a spot just shoot me an IM/PM here and ask me to take a look. I usually have enough time
to do a build and step through something.

I did 3 docker HOWTOs over here...
Nothing fancy, I just wanted a feel for it, and those are the results.

Peace out!

PS. If you want bash to run in the container, use
or even a
CMD directive using
or a slight (syntax) variation, eg: something like that.

But if you run /bin/bash, and you enter the container, you have to detach from it for the container to stay running.
Since bash is the command holding the container 'open', you have to detach, not 'exit'.

Reference:
https://docs.docker.com/reference/builder/

I use the same Dockerfiles on either OS.
Running an Ubuntu container in a CentOS environment is perfectly fine, or vice versa for that matter.

Hmm, some are saying Ubuntu docker images should run on an Ubuntu host.

By the way, I sent you a friend request.

How do you PM in this website?

Do you know automation tools like Puppet too?

I'd like to see that reference.

Got it.

Try this

No, I do not. No puppet, no chef, no ansible.
Doesn't mean I won't need those skills, as we are a Managed Service Provider and our flagship product (AppLogic) is EOL at the end of June.

So, things are about to get interesting where I work.

Hmm, I don't have permission to access that page to PM.

Can you send me a PM with your AIM or any messenger ID? if not, we can just talk on this forum.

Oh and by the way, reviewed the Docker course again and turns out I was supposed to comment out the last tine (LOL)
Peace!