buildDockerImage.sh fails with 12.2.0.1 se (chown: changing ownership of '/opt/oracle/install/linuxx64_12201_database.zip': File too large)

[lurodrig]

Hello there,

It is me again , now trying to build Oracle Database 12.2.0.1 se, you can have a look at buildDockerImage from https://github.com/oracle/docker-images fails with 11.2.0.2 xe

Same host:

CentOS Linux release 7.2.1511 (Core)
Linux version 3.10.0-327.10.1.el7.x86_64 (builder@kbuilder.dev.centos.org) (gcc version 4.8.3 20140911 (Red Hat 4.8.3-9) (GCC) ) #1 SMP Tue Feb 16 17:03:50 UTC 2016

Now trying...

./buildDockerImage.sh -v 12.2.0.1 -s -i

I get:

Complete!  
Loaded plugins: ovl  
Cleaning repos: ol7_UEKR4 ol7_latest  
Cleaning up everything  
chown: changing ownership of '/opt/oracle/install/linuxx64_12201_database.zip': File too large  
Removing intermediate container 6622686f4e18  
The command '/bin/sh -c chmod ug+x $INSTALL_DIR/*.sh &&     sync &&     $INSTALL_DIR/$CHECK_SPACE_FILE &&     $INSTALL_DIR/$SETUP_LINUX_FILE' returned a non-zero code: 1  
There was an error building the image.

Am I missing something? Apart that perhaps I can try to rename the binaries file to something shorter...

Thanks in advance,

Luis

[gvenzl]

Hi @lurodrig, I don't think that it has to do with the filename but rather with the file size. Although I have never seen chown failing with such an error. Perhaps this is due to some file system limitation? Which fs are you using inside your container?

[lurodrig]

Hello @gvenzl. Yes, you are right, I've just realized that it was nothing to do with the file name, I was very naive... :)

Abot the fs (thanks, good hint!):

The host machine (Centos7):

[dockerfiles]$ df -T -h /dev/mapper/cc_xxxx-home
Filesystem                            Type   Size    Used   Avail   Use%   Mounted on
/dev/mapper/cc_xxxx-home  xfs      94G   11G     84G    12%      /home

And inside the container (not 100% sure if this is you are asking me...):

Step 7/17 : RUN df -T -h
 ---> Running in f80559f3fc3b
Filesystem                    Type     Size  Used Avail Use% Mounted on
overlay                              overlay   50G   34G   17G  67% /
tmpfs                                 tmpfs    2.3G     0  2.3G   0% /dev
tmpfs                                 tmpfs    2.3G     0  2.3G   0% /sys/fs/cgroup
/dev/mapper/cc_xxxx-root xfs       50G   34G   17G  67% /etc/hosts
shm                                   tmpfs     64M     0   64M   0% /dev/shm
tmpfs                                 tmpfs    2.3G     0  2.3G   0% /sys/firmware

Thanks in advance,

Luis

[gvenzl]

This looks good to me. @Djelibeybi, do you have any idea why chown would fail with this error?

[mknies]

I have the same problem... Filesystem xfs on OL7.3...

$: chown oracle:dba linuxx64_12201_database.zip
chown: changing ownership of 'linuxx64_12201_database.zip': File too large

bash-4.2# df -hT (Inside the container...)
Filesystem Type Size Used Avail Use% Mounted on
overlay overlay 41G 17G 25G 41% /
tmpfs tmpfs 496M 0 496M 0% /dev
tmpfs tmpfs 496M 0 496M 0% /sys/fs/cgroup
/dev/mapper/ol-root xfs 41G 17G 25G 41% /etc/hosts
shm tmpfs 64M 0 64M 0% /dev/shm
tmpfs tmpfs 496M 0 496M 0% /sys/firmware

[chrisguoado]

@sniper66 @gvenzl I'm not sure the root cause of this issue, it looks there's sufficient disk space. While we definitely should avoid chown'ing large files like linuxx64_12201_database.zip during the image building. chown actually adds new image layer thus makes the built image that file size larger.

[mknies]

@chrisguoado Thank you for your reply...
I can´t do anything with that file...

Just take a look here:
bash-4.2# chmod 777 linuxx64_12201_database.zip
chmod: changing permissions of 'linuxx64_12201_database.zip': File too large
bash-4.2# mv linuxx64_12201_database.zip linuxx64_12201_database.zip_test
mv: cannot move 'linuxx64_12201_database.zip' to 'linuxx64_12201_database.zip_test': File too large
bash-4.2# cat /etc/oracle-release
Oracle Linux Server release 7.3
bash-4.2# uname -a
Linux ad0cb32cda6c 4.1.12-61.1.28.el7uek.x86_64 #2 SMP Thu Feb 23 19:55:12 PST 2017 x86_64 x86_64 x86_64 GNU/Linux

On the host OL7.3 I can do a chmod, chown etc....

[chrisguoado]

Yes, it certainly only relates to the operations in the container. But I guess you should be able to unzip the file, and then remove it. If so, it looks like there's something wrong or limitation with the driver handling new layers on the (xfs) FS.

[mknies]

Yes, unzipping and removing works in the container...

[mknies]

Does anyone know which limitations that could be???

[lurodrig]

I do think that this issue is related with #326

@sniper66 perhaps you could try docker info and look for Data Space Total

You can have a look at https://jpetazzo.github.io/2014/01/29/docker-device-mapper-resize/

Cheers,

Luis

[mknies]

I already changed it to overlay2...

Storage Driver: overlay2
Backing Filesystem: xfs
Supports d_type: false
Native Overlay Diff: false

[lurodrig]

Hello there,

Extending the docker Base Device Size to 20GB did the trick for me. I configured it via /etc/docker/daemon.json See Configure the Docker daemon with specific devicemapper options. on https://docs.docker.com/engine/userguide/storagedriver/device-mapper-driver/#configure-direct-lvm-mode-for-production

My /etc/docker/daemon.json looks like:

{
    "live-restore": true,
    "storage-opts": ["dm.basesize=20G"]
}

Hope it helps,

Luis

ps: thanks for all your responses