mkdir -p ~/vagrant/centos7-minimal
cd ~/vagrant/centos7-minimal
vagrant init uvsmtid/centos-7.0-minimal
A `Vagrantfile` has been placed in this directory. You are now
ready to `vagrant up` your first virtual environment! Please read
the comments in the Vagrantfile as well as documentation on
`vagrantup.com` for more information on using Vagrant.

vagrant global-status
id name provider state directory
------------------------------------------------------------------------
5b3e766 default libvirt running /home/rsoares/vagrant/centos7-minimal
The above shows information about all known Vagrant environments
on this machine. This data is cached and may not be completely
up-to-date. To interact with any of the machines, you can go to
that directory and run Vagrant, or you can use the ID directly
with Vagrant commands from any directory. For example:
"vagrant destroy 1a2b3c4d"

Maybe you are thinking… WTF! Why have this guy written this post in English?!

Well,
I think this is my first blog post in this blog written in en_US. The motivation is simple. The subject (Docker and all the related things around it) is attracting almost all the attention of IT at this moment. So the basic idea is to help more people that might face the same issue described in this post.

So, please ignore any language/typo mistake.

😉

Ok!

For those trying to build a RHEL 7 Docker Base Image with Java 7 support (OpenJDK 7 packages), the openjdk pkgs depends on systemd. When you try to install the openjdk via yum you may see the following error:

The rhel7 official base image includes a fakesystemd (from @koji-override-0/7.0 repo) instead of full systemd. I’m not sure if this fafesystemd pkg is shipped with rhel 7 docker base image (I have to check to confirm). I saw some blogs posts saying it is used to avoid a number of bad implications with running full systemd on Docker Containers. I thik it come as a dependence with the openssh-server pkg I’ve installed before. This fakesystemd provides only some fake files to satisfy some other pkgs requirements that depends on systemd service:

# General configuration for the init.d scripts,
# not necessarily for JBoss AS itself.
# Path to JBoss EAP Installation
JBOSS_HOME=/opt/redhat/jboss-eap-6.3
# The username who should own the process.
#
JBOSS_USER=jboss
# The amount of time to wait for startup
#
STARTUP_WAIT=30
# The amount of time to wait for shutdown
#
SHUTDOWN_WAIT=30
# Location to keep the console log
#
JBOSS_CONSOLE_LOG=/var/log/jboss-as/console.log
# JBoss configuration file
JBOSS_CONFIG=standalone.xml
# Public IP Address where JBoss will listen
JBOSS_PUB_BIND=192.168.122.65
# Management IP Address where JBoss will listen
JBOSS_MGMT_BIND=192.168.122.65

-bash-4.2$ createuser -d -l -P --interactive NEW_DB_USER
Enter password for new role:
Enter it again:
Shall the new role be a superuser? (y/n) n
Shall the new role be allowed to create more new roles? (y/n) n