Problem instantiating Hipperos contaitner

Available to be read by all.
A_Konstantinos
Posts: 7
Joined: Wed Jul 25, 2018 12:34 pm

Problem instantiating Hipperos contaitner

Postby A_Konstantinos » Tue Jul 31, 2018 2:51 pm

After i run the setupHost.sh and followed the steps on 6.1 Generic installation procedure for Linux(userGuide) i try to run the hipperos_container_run in order to instantiate a Hipperos container but i get the following error :
"docker: Error response from daemon: invalid mount config for type "bind": bind source path does not exist"

The path that causes this problem is the following

dockerBinDir="$( cd "$( dirname "${BASH_SOURCE[0]}" )" && pwd )"
hipperosDistributionDir=$(realpath "${dockerBinDir}/..")
defaultArgs="\
--interactive=true \
--rm \
--device-cgroup-rule=\"a ${ttyDeviceMajorNum}:* rwm\" \
--tty=true \
--mount type=bind,source=${hipperosDistributionDir},target=/hipperos/distribution \

but it's a perfectly legal path that totally exists. So after that, i changed this directory with my home directory on the ./hipperos_container_run but still i get this error :

"docker: Error response from daemon: OCI runtime create failed: container_linux.go:348: starting container process caused "process_linux.go:402: container init caused \"mkdir /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release: permission denied\"": unknown."

Do you have any clue what is going on because i am really stuck.I didnt find anything useful on the internet about these errors..
Thank you for your time..

Vladimir_Svoboda
Posts: 5
Joined: Fri Feb 02, 2018 11:47 am
Location: Brussels

Re: Problem instantiating Hipperos contaitner

Postby Vladimir_Svoboda » Tue Jul 31, 2018 5:18 pm

First, backup your changes in the file "hipperos_container_run" and then revert it to its original state.

Maybe this is an access right issue. Are you sure that you added your user inside the "docker" group? To do it, execute this command

Code: Select all

sudo usermod -aG docker $(id -un)

And reboot your machine afterwards.

After the reboot, run the container as described in the user guide. If it still fails, execute this instead

Code: Select all

bash -x ./hipperos_container_run
and post the output here.

Thank you.

A_Konstantinos
Posts: 7
Joined: Wed Jul 25, 2018 12:34 pm

Re: Problem instantiating Hipperos contaitner

Postby A_Konstantinos » Wed Aug 01, 2018 11:26 am

So this is the output that i get after i did what you proposed , the error remains though..
+ additionalArgs=
+ cmd=
+++ dirname ./hipperos_container_run
++ cd .
++ pwd
+ dockerBinDir=/homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp/bin
++ head -n 1 /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp/bin/container_id.txt
+ containerId=hipperos_18.06_tulipp_te0715_te0715_elf_hardfp
++ head -n 1 /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp/bin/container_version.txt
+ imageVersion=2018.06.07-1
+ label=hipperos_18.06_tulipp_te0715_te0715_elf_hardfp_2018.06.07-1
++ realpath /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp/bin/..
+ hipperosDistributionDir=/homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp
++ /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp/bin/../setup/makeflags.sh
+ makeFlags='-j5 -l4'
+ registry=registry.containers.ovh.net/hipperos
+ image=registry.containers.ovh.net/hipperos/hipperos_base:2018.06.07-1
+ docker pull registry.containers.ovh.net/hipperos/hipperos_base:2018.06.07-1
2018.06.07-1: Pulling from hipperos/hipperos_base
Digest: sha256:962c3b371260d964993d6cf6a10ba3df0d78ebda37cd1413eba74792653fd147
Status: Image is up to date for registry.containers.ovh.net/hipperos/hipperos_base:2018.06.07-1
+ ttyDeviceMajorNum=188
++ id -u
++ id -g
++ id -un
++ id -gn
++ pwd
+ defaultArgs=' --interactive=true --rm --device-cgroup-rule="a 188:* rwm" --tty=true --mount type=bind,source=/homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp,target=/hipperos/distribution --user 1093:500 --group-add uucp --group-add plugdev --group-add dialout --env RUNNER_USER=kasteriou --env RUNNER_GROUP=thinksilicon --env MAKEFLAGS="-j5 -l4" --env force_color_prompt=yes --mount type=bind,source=/tmp/.X11-unix,target=/tmp/.X11-unix --mount type=bind,source=/homes/Patras-BR/kasteriou/.Xauthority,target=/tmp/.Xauthority --env DISPLAY=unix:0.0 --env XAUTHORITY=/tmp/.Xauthority --mount type=volume,source=hipperos_cots,target=/hipperos/cots --mount type=volume,source=hipperos_home,target=/container/home --mount type=bind,source=/homes/Patras-BR/kasteriou,target=/homes/Patras-BR/kasteriou --workdir /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp/bin --label hipperos --label hipperos_18.06_tulipp_te0715_te0715_elf_hardfp_2018.06.07-1'
+ fullCmd='docker run --interactive=true --rm --device-cgroup-rule="a 188:* rwm" --tty=true --mount type=bind,source=/homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp,target=/hipperos/distribution --user 1093:500 --group-add uucp --group-add plugdev --group-add dialout --env RUNNER_USER=kasteriou --env RUNNER_GROUP=thinksilicon --env MAKEFLAGS="-j5 -l4" --env force_color_prompt=yes --mount type=bind,source=/tmp/.X11-unix,target=/tmp/.X11-unix --mount type=bind,source=/homes/Patras-BR/kasteriou/.Xauthority,target=/tmp/.Xauthority --env DISPLAY=unix:0.0 --env XAUTHORITY=/tmp/.Xauthority --mount type=volume,source=hipperos_cots,target=/hipperos/cots --mount type=volume,source=hipperos_home,target=/container/home --mount type=bind,source=/homes/Patras-BR/kasteriou,target=/homes/Patras-BR/kasteriou --workdir /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp/bin --label hipperos --label hipperos_18.06_tulipp_te0715_te0715_elf_hardfp_2018.06.07-1 registry.containers.ovh.net/hipperos/hipperos_base:2018.06.07-1 '
+ echo /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp
/homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp
+ echo 'You will be prompted for the sudo password in order to connect devices that are already plugged in.'
You will be prompted for the sudo password in order to connect devices that are already plugged in.
+ sudo true
+ sleep 2
+ eval docker run --interactive=true --rm '--device-cgroup-rule="a' '188:*' 'rwm"' --tty=true --mount type=bind,source=/homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp,target=/hipperos/distribution --user 1093:500 --group-add uucp --group-add plugdev --group-add dialout --env RUNNER_USER=kasteriou --env RUNNER_GROUP=thinksilicon --env 'MAKEFLAGS="-j5' '-l4"' --env force_color_prompt=yes --mount type=bind,source=/tmp/.X11-unix,target=/tmp/.X11-unix --mount type=bind,source=/homes/Patras-BR/kasteriou/.Xauthority,target=/tmp/.Xauthority --env DISPLAY=unix:0.0 --env XAUTHORITY=/tmp/.Xauthority --mount type=volume,source=hipperos_cots,target=/hipperos/cots --mount type=volume,source=hipperos_home,target=/container/home --mount type=bind,source=/homes/Patras-BR/kasteriou,target=/homes/Patras-BR/kasteriou --workdir /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp/bin --label hipperos --label hipperos_18.06_tulipp_te0715_te0715_elf_hardfp_2018.06.07-1 registry.containers.ovh.net/hipperos/hipperos_base:2018.06.07-1
++ docker run --interactive=true --rm '--device-cgroup-rule=a 188:* rwm' --tty=true --mount type=bind,source=/homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp,target=/hipperos/distribution --user 1093:500 --group-add uucp --group-add plugdev --group-add dialout --env RUNNER_USER=kasteriou --env RUNNER_GROUP=thinksilicon --env 'MAKEFLAGS=-j5 -l4' --env force_color_prompt=yes --mount type=bind,source=/tmp/.X11-unix,target=/tmp/.X11-unix --mount type=bind,source=/homes/Patras-BR/kasteriou/.Xauthority,target=/tmp/.Xauthority --env DISPLAY=unix:0.0 --env XAUTHORITY=/tmp/.Xauthority --mount type=volume,source=hipperos_cots,target=/hipperos/cots --mount type=volume,source=hipperos_home,target=/container/home --mount type=bind,source=/homes/Patras-BR/kasteriou,target=/homes/Patras-BR/kasteriou --workdir /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp/bin --label hipperos --label hipperos_18.06_tulipp_te0715_te0715_elf_hardfp_2018.06.07-1 registry.containers.ovh.net/hipperos/hipperos_base:2018.06.07-1
docker: Error response from daemon: invalid mount config for type "bind": bind mount source path does not exist: /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp.

Vladimir_Svoboda
Posts: 5
Joined: Fri Feb 02, 2018 11:47 am
Location: Brussels

Re: Problem instantiating Hipperos contaitner

Postby Vladimir_Svoboda » Wed Aug 01, 2018 2:58 pm

The docker daemon is a system process and for some reason it seems that it has no access to this directory.
I am surprised that your home directory is located in a "/homes" folder. Is it located on a network disk?

Can you execute these commands and post the output?

Code: Select all

namei -l /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp

Code: Select all

cat /etc/fstab | grep "/homes"

A_Konstantinos
Posts: 7
Joined: Wed Jul 25, 2018 12:34 pm

Re: Problem instantiating Hipperos contaitner

Postby A_Konstantinos » Wed Aug 01, 2018 3:13 pm

The output on the first command
"f: /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release/hipperos_18.06_tulipp_te0715_te0715_elf_hardfp
drwxr-xr-x root root /
drwxr-xr-x root root homes
drwxr-xr-x root patras-br Patras-BR
drwxr-xr-x kasteriou thinksilicon kasteriou
drwxr-xr-x kasteriou thinksilicon Desktop
drwxr-xr-x kasteriou thinksilicon HIPPEROS
drwxr--r-- kasteriou thinksilicon HIPPEROS_Distrib_ThinkSilicon
drwxr--r-- kasteriou thinksilicon hipperos_180600_20180608_release
drwxrwxrwx kasteriou thinksilicon hipperos_18.06_tulipp_te0715_te0715_elf_hardfp"

and the output on the second one
"192.168.1.9:/homes /homes nfs nfsvers=4.1,fsc,bg,rw,auto,noatime,nolock,actimeo=1800,tcp,rsize=32768,wsize=32768,timeo=900,retrans=4 0 0"

And yes the /homes folder is located on a network disk

Vladimir_Svoboda
Posts: 5
Joined: Fri Feb 02, 2018 11:47 am
Location: Brussels

Re: Problem instantiating Hipperos contaitner

Postby Vladimir_Svoboda » Wed Aug 01, 2018 5:45 pm

it seems that the issue is related to the fact that your home directory is a NFS mount point.
I see 3 possible fixes for the issue.

First solution

Extract the distribution to a directory which is not on a network disk.
You do not need to perform the setup again.
Remove the line "--mount type=bind,source=$HOME,target=$HOME \" in the file "hipperos_container_run" of the newly extracted distribution directory.
And then run "hipperos_container_run" from the newly extracted distribution directory.

Second solution

Execute these commands

Code: Select all

chmod +x /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/
chmod +x /homes/Patras-BR/kasteriou/Desktop/HIPPEROS/HIPPEROS_Distrib_ThinkSilicon/hipperos_180600_20180608_release

Replace the lines with the "--mount" argument that fails with:

Code: Select all

--mount 'type=volume,source=<NAME>,target=<DEST>,volume-driver=local,volume-opt=type=nfs,volume-opt=device=192.168.1.9:/homes,"volume-opt=o=addr=192.168.1.9,vers=4,soft,timeo=900,bg,tcp,rw,rsize=32768,wsize=32768,retrans=4"' \

Don't forget to update the <NAME> and <DEST> part of the line.
For each modified line, the <NAME> must be unique.
And for each of the source name you give, I think you should first execute

Code: Select all

docker volume create <NAME>


Third solution

Based on the original "hipperos_container_run" file, add --privileged=true as argument to the docker run command.

A_Konstantinos
Posts: 7
Joined: Wed Jul 25, 2018 12:34 pm

Re: Problem instantiating Hipperos contaitner

Postby A_Konstantinos » Thu Aug 02, 2018 10:35 am

Installing collected packages: hipperos
Successfully installed hipperos-18.6
Thank you so much for your help :)

Vladimir_Svoboda
Posts: 5
Joined: Fri Feb 02, 2018 11:47 am
Location: Brussels

Re: Problem instantiating Hipperos contaitner

Postby Vladimir_Svoboda » Thu Aug 02, 2018 1:24 pm

You're welcome :)
Can you just tell me which solution you have chosen ? :)
Thanks for your feedback.


Return to “FAQ about Tulipp Development Platform”

Who is online

Users browsing this forum: No registered users and 11 guests