Problem in extracting yocto SDK for docker

Actually I was facing the following issue while building my Yocto SDK on Docker container

sudo docker build --tag="akash/eclipse-che:6.5.0-1" --tag="akash/eclipse-che:latest" /home/akash/dockerimage.yocto.support/
Sending build context to Docker daemon  26.93MB
Step 1/5 : FROM eclipse/cpp_gcc
 ---> 8397ec8fd9d1
Step 2/5 : ENV META_TOOLCHAIN=poky-glibc-x86_64-meta-toolchain-cortexa7hf-neon-vfpv4-toolchain-2.4.3.sh
 ---> Using cache
 ---> b6efe9fb9be4
Step 3/5 : RUN wget -O /tmp/$META_TOOLCHAIN "<link for toolchain >=$META_TOOLCHAIN"
 ---> Using cache
 ---> 674e007553da
Step 4/5 : RUN chmod +x /tmp/$META_TOOLCHAIN
 ---> Using cache
 ---> 5f558946851e
Step 5/5 : RUN /tmp/$META_TOOLCHAIN
 ---> Running in b5909d0fe10c
Poky (Yocto Project Reference Distro) SDK installer version 2.4.3
=================================================================
You are about to install the SDK to "/home/akash/rpil/rpi-build/tmp". Proceed[Y/n]? Extracting SDK.............done
Setting it up...ls: cannot access '/home/akash/rpil/rpi-build/tmp/environment-setup-cortexa7hf-neon-vfpv4-poky-linux-gnueabi': No such file or directory
SDK relocate failed, could not get executalbe files
The command '/bin/sh -c /tmp/$META_TOOLCHAIN' returned a non-zero code: 1

environment-setup-cortexa7hf-neon-vfpv4-poky-linux-gnueabi file is actually present in the tmp directory.I am not able to understand why it cannot access it.

I have noticed that my sysroots directory is empty.I am just assuming that that may be the reason for the issue.

This is the some part of the shell script of SDK which is being extracted.

tail -n +$payload_offset $0| $SUDO_EXEC tar xJ -C $target_sdk_dir --checkpoint=.2500 $EXTRA_TAR_OPTIONS || exit 1
echo "done"

printf "Setting it up..."
# fix environment paths
real_env_setup_script=""
for env_setup_script in `ls $target_sdk_dir/environment-setup-cortexa7hf-neon-vfpv4-poky-linux-gnueabi`; do
        if grep -q 'OECORE_NATIVE_SYSROOT=' $env_setup_script; then
                # Handle custom env setup scripts that are only named
                # environment-setup-* so that they have relocation
                # applied - what we want beyond here is the main one
                # rather than the one that simply sorts last
                real_env_setup_script="$env_setup_script"
        fi
        $SUDO_EXEC sed -e "s:/opt/poky/2.4.3:$target_sdk_dir:g" -i $env_setup_script
done
 if [ -n "$real_env_setup_script" ] ; then

Note: I am unable to post the link because this is my fifth post.

Is /home/akash/rpil/rpi-build/tmp/ writable by user root?

I even tried it without using sudo but it shows the same error.I even tried to change the directory path to /opt/poky/2.4.3 but it still did not worked out.And yes ,it has root permissions.

Is /home/akash/rpil/rpi-build/tmp created in your Dockerfile?

RUN mkdir -p /home/akash/rpil/rpi-build/tmp

Andrew