Hi Brien,
I have followed the below steps:
1) pulled image from nexus3.org.onap -->/onap/aai-graphadmin:1.0-STAGING-latest
2) created container using "docker run -d -p 8449:8449 <image-name>"
3) inside the graphadmin container added attributes and new edgerules-
in resources/schema/onap/oxm/v14 and resources/schema/onap/dbedgerules/v14
4) then did "docker commit container-name new-image-name"
What is the difference when image is built from Dockerfile and when image is
created doing docker commit on container.
5)Used the above image and deployed on k8's environment using helm.
The below two pods are not running:
dev-aai-aai-graphadmin-96779b95b-5sq7q ---stays in init mode
dev-aai-aai-graphadmin-create-db-schema-fm9t8 ----stays in running mode
instead of completed[Error:The graphadmin microservice is started and does not
execute the createDbSchema script.]
Please help me through this. I am stuck here for a very long time.
Regards,
Ambica
________________________________
From: [email protected] <[email protected]> on behalf of
Ambica <[email protected]>
Sent: Friday, April 19, 2019 8:01 PM
To: KAJUR, HARISH V; [email protected]; [email protected]
Subject: Re: [onap-discuss] aai-graphadmin pod start error in k8 using helm
I wanted a new image that would reflect the changes made in aai_oxm_v14.xml and
Dbedgerules_v14.json file in aai-graphadmin .
Can we create a new image from a modified container using DockerFile.If Yes,
Can you please share the commands.
Regards,
Ambica
________________________________
From: KAJUR, HARISH V <[email protected]>
Sent: Friday, April 19, 2019 7:24 PM
To: Ambica Chattoraj; [email protected]; [email protected]
Subject: RE: [onap-discuss] aai-graphadmin pod start error in k8 using helm
Hi Ambica,
I sent the link as a reference as they are facing an similar issue due to the
fact they are trying to mount a directory on the host machine to a file inside
the container.
This was the error that you are seeing right:
kubelet, onap-k8s-2.mgmt Error: Error response from daemon: cannot mount
volume over existing file, file exists
/var/lib/docker/overlay/a7a05a40cfc65adfb4a7646794fb5dd9b2abf03a57c4b9550adde1949e4b948f/merged/opt/app/aai-graphadmin/resources/etc/auth/realm.properties
Note:-There is no folder
"a7a05a40cfc65adfb4a7646794fb5dd9b2abf03a57c4b9550adde1949e4b948f" in
/var/lib/docker/overlay.
>From this error, it seems to be the case that within the container there is a
>file called: /opt/app/aai-graphadmin/resources/etc/auth/realm.properties
But for some reason, you seem to be mounting an directory on that location as
that could be the reason causing it.
If that isn’t the case, I would suggest you go do the following on the new
image and old image:
docker run -it --rm --entrypoint=/bin/bash
nexus3.onap.org:10001/onap/aai-graphadmin:1.0-STAGING-latest
Then go to the /opt/app/aai-graphadmin folder and look at all the sub
directories and files and try to identify the difference between
1.0-STAGING-latest and your committed container.
If you see that one is a file in the 1.0-STAGING-latest and the image you
created is a directory, that could be the culprit.
Also, why did you commit the running container to create a new image instead of
just creating an new docker image from Dockerfile?
Thanks,
Harish
From: Ambica Chattoraj <[email protected]>
Sent: Friday, April 19, 2019 3:53 AM
To: KAJUR, HARISH V <[email protected]>; [email protected];
[email protected]
Subject: Re: [onap-discuss] aai-graphadmin pod start error in k8 using helm
Hi Harsh,
>From the link you have forwarded it is unclear what exactly need to be run.
>The commands specified are for running the image .
Can you please tell where exactly i need to remove/make changes inside the
container .so that when creating new image doing commit does not use the
previous mount location.
Thanks & Regards,
Ambica
________________________________
From: KAJUR, HARISH V <[email protected]<mailto:[email protected]>>
Sent: Thursday, April 18, 2019 10:41 PM
To: [email protected]<mailto:[email protected]>;
[email protected]<mailto:[email protected]>; Ambica Chattoraj
Subject: RE: [onap-discuss] aai-graphadmin pod start error in k8 using helm
Hi Ambica,
>From the error that you are getting, you seem to be voluming a directory where
>a file already exists in the container.
You can volume a file to file or a directory from host to directory in
container but if you try to volume from host a directory where there is an file
in the container it doesn't work.
Please look at this stackoverflow question as a reference:
https://stackoverflow.com/questions/33903621/docker-cannot-mount-volume-over-existing-file-file-exists<https://urldefense.proofpoint.com/v2/url?u=https-3A__stackoverflow.com_questions_33903621_docker-2Dcannot-2Dmount-2Dvolume-2Dover-2Dexisting-2Dfile-2Dfile-2Dexists&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=f44eG3iZaja2ozEA2yRZnQ&m=AuENRpNSVsn61GXaf8hwXngEKc_2k_BeJEtU_lhr7zM&s=lv19luxnwxZoUJWrVgA59VY0S0-s6GkAbTnTAtic8aM&e=>
Please take a look inside your docker container from your new image to the old
image on the path that its complaining to see when you did the docker commit.
Thanks,
Harish
-----Original Message-----
From: [email protected]<mailto:[email protected]>
<[email protected]<mailto:[email protected]>> On Behalf Of
Keong Lim
Sent: Thursday, April 18, 2019 10:42 AM
To: Ambica <[email protected]<mailto:[email protected]>>;
[email protected]<mailto:[email protected]>
Subject: Re: [onap-discuss] aai-graphadmin pod start error in k8 using helm
Hi Ambica,
Sorry I will be on leave for Easter. I don't know what is happening with the
overlay filesystem in this case.
Maybe Harish can help you debug it.
Keong
============================================================================================================================
Disclaimer: This message and the information contained herein is proprietary
and confidential and subject to the Tech Mahindra policy statement, you may
review the policy at
http://www.techmahindra.com/Disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__www.techmahindra.com_Disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=f44eG3iZaja2ozEA2yRZnQ&m=AuENRpNSVsn61GXaf8hwXngEKc_2k_BeJEtU_lhr7zM&s=w5f-9NwakN63S01O4VRFYJ2OCQufF_f3eVGTJ4_TnKs&e=>
externally
http://tim.techmahindra.com/tim/disclaimer.html<https://urldefense.proofpoint.com/v2/url?u=http-3A__tim.techmahindra.com_tim_disclaimer.html&d=DwMFAg&c=LFYZ-o9_HUMeMTSQicvjIg&r=f44eG3iZaja2ozEA2yRZnQ&m=AuENRpNSVsn61GXaf8hwXngEKc_2k_BeJEtU_lhr7zM&s=l7DPkOAvrL69ooGOIzUVsKlxkuDezk8RR8soPYt2ckk&e=>
internally within TechMahindra.
============================================================================================================================
-=-=-=-=-=-=-=-=-=-=-=-
Links: You receive all messages sent to this group.
View/Reply Online (#16684): https://lists.onap.org/g/onap-discuss/message/16684
Mute This Topic: https://lists.onap.org/mt/31223382/21656
Group Owner: [email protected]
Unsubscribe: https://lists.onap.org/g/onap-discuss/unsub
[[email protected]]
-=-=-=-=-=-=-=-=-=-=-=-
