Data Matters

I installed Oracle 11.2.0.3 in a Centos 7 docker container with following steps: Setup bigger /dev/shm for the docker container, you may follow http://data-matters.blogspot.com/2016/02/config-size-of-shared-memorydevshm-for.html Install dependencies: yum -y install gcc gcc-c++ libaio-devel make Setup a rsp file for install, just follow https://gist.github.com/arnobroekhof/8465884 http://nervinformatica.com.br/blog/?p=2303 Edit stage/cvu/cvu_prereq.xml, make RUNLEVEL check IGNORABLE. The step is based on http://www.torkwrench.com/2014/10/16/automating-oracle-11-2-installation-on-rhel-7/ Install with runInstaller script: ./runInstaller -silent -responseFile /path/to/rspfile

Due to the issue from github , the size of shared memory is fixed at 64M. If you want larger size /dev/shm, please upgrade your docker to version newer than 1.10, and specify --shm-size when you run a docker image. Below is the help message of --shm-size. --shm-size="" Size of /dev/shm. The format is . number must be greater than 0. Unit is optional and can be b (bytes), k (kilobytes), m (megabytes), or g (gigabytes). If you omit the unit, the system uses bytes. If you omit the size entirely, the system uses 64m.

After upgraded Python 2.7 to latest version, it may occur to _PyErr_ReplaceException sometimes in virtualenv created by former version of python. For example: >>> import io Traceback (most recent call last): File " ", line 1, in File "/usr/lib/python2.7/io.py", line 51, in import _io ImportError: /home/ubuntu/ikaka/leanStudy/venv/lib/python2.7/lib-dynload/_io.so: undefined symbol: _PyErr_ReplaceException This is because the virtualenv had copied the python executable binary but linked lib directory. So just replace the python executable binary in virtualenv with the one in /usr/lib, like cp /usr/bin/python /bin/python

When run(start) a docker container from an image, we can specify the default user by passing -u option in command line(In https://docs.docker.com/engine/reference/run/#user ). For example docker run -i -t -u ubuntu ubuntu:latest /bin/bash We can also use the USER instruction in DOCKERFILE to do the same thing(In https://docs.docker.com/engine/reference/builder/#user), note that the option in command line will override the one in the DOCKERFILE. And there is actually another way to start a container with neither DOCKERFILE nor -u option, just by a command like: docker run -i -t ubuntu:latest /bin/bash # with ubuntu as the default user This happens when your start the container from an image committed by a container with ubuntu as the default user. Or in detail: Run a container from some basic images, create ubuntu user inside it, commit the container to CUSTOM_IMAGE:1 . Run a container from CUSTOM_IMAGE:1 with "-u ubuntu" option, and commit the container to CUSTOM

Packages in git repo (or hg, svn, bzr) can be installed with " pip install -e " directly. Base on the help message of " pip install ", we have -e VCS+REPOS_URL[@REV]#egg=PACKAGE, --editable=VCS+REPOS_URL[@REV]#egg=PACKAGE Install a package directly from a checkout. Source will be checked out into src/PACKAGE (lower-case) and installed in-place (using setup.py develop). You can run this on an existing directory/checkout (like pip install -e src/mycheckout). This option may be provided multiple times. Possible values for VCS are: svn, git, hg and bzr. To use it, first make sure you have git installed. Such as " sudo apt-get install git-core " on ubuntu. And then you may follow the below examples(install redis-py): # Install from master pip install -e git+https://github.com/andymccurdy

The official document of mariadb does not mention the default CREATE TABLE options for tables using Aria Engine.  The default options are list as below: TRANSACTIONAL,  the default value is TRANSACTIONAL=0, i.e., non-transactional. ROW_FORMAT, the default value is ROW_FORMAT=PAGE, which may suits both transactional and non-transactional tables. PAGE_CHECKSUM,  the default value will follow aria_page_checksum system variable, which has default value ON. For the TRANSACTIONAL option, you may consider create a table as below(and ALTER the TRANSACTIONAL=1): CREATE TABLE `test_table` ( `id` int(11) NOT NULL AUTO_INCREMENT, PRIMARY KEY (`id`) ) ENGINE=Aria; If you change the ROW_FORMAT to DYNAMIC or FIXED, everything just goes fine. But if you have ALTER the table with TRANSACTION=1 and change the ROW_FORMAT to DYNAMIC or FIXED, you may got a warning: SHOW WARNINGS; +-------+------+----------------------------------------------------------+ | Level | Code | Message | +-------+--