# apt-get install --reinstall -o Dpkg::Options::="--force-confmiss" apache2
Reading package lists... Done
Building dependency tree
Reading state information... Done
0 upgraded, 0 newly installed, 1 reinstalled, 0 to remove and 5 not upgraded.
Need to get 86,7 kB of archives.
After this operation, 0 B of additional disk space will be used.
Get:1 http://archive.ubuntu.com/ubuntu/ saucy-updates/main apache2 amd64 2.4.6-2ubuntu2.1 [86,7 kB]
Fetched 86,7 kB in 0s (264 kB/s)
(Reading database ... 245864 files and directories currently installed.)
Preparing to replace apache2 2.4.6-2ubuntu2.1 (using .../apache2_2.4.6-2ubuntu2.1_amd64.deb) ...
Unpacking replacement apache2 ...
Processing triggers for man-db ...
Processing triggers for ufw ...
Processing triggers for ureadahead ...
ureadahead will be reprofiled on next reboot
Setting up apache2 (2.4.6-2ubuntu2.1) ...
Configuration file `/etc/apache2/sites-available/000-default.conf', does not exist on system.
Installing new config file as you requested.
* Restarting web server apache2
Practical scenario #2
There’s another interesting case when this procedure comes handy: if you changed a default etc file and you want to restore it. In that case you can simply delete it and use the same apt-get command:
Testing docker is really interesting, but sometimes it’s difficult to understand what’s wrong with some configuration.
A problem I found recently dealed with the ADD directive used in the Dockerfile. I was trying to start some services with supervisor but I got this error during the image build process
Step 19 : ADD supervisord.conf /etc/supervisor/conf.d/
2014/02/10 00:40:55 build: supervisord.conf: no such file or directory
The file was right there, in the same path of the Dockerfile, but docker couldn’t find it.
After a good read of the official documentation I learned the conxept of “build context”. When you are building an image, the source directory from which you are operating is the build context, but when you are building passing the Dockerfile from the standard input, there’s no build context!
So this is ok
$ docker build -t mydebian .
and this can’t work
$ docker build -t mydebian - < Dockerfile
The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.