[Starlingx-discuss] docker instance cannot boot (no boot device)
Hi, I created in openstack an image of the docker type. When an instance of that image starts, the console shows the SeaBIOS version followed by ipxe and the last message is "No bootable device": it looks like as if openstack is trying to create a VM instead of a container. openstack shows the "container_format" of the image as "docker". The same docker image runs fine on the same controller host when started by hand (docker load, followed by docker run). I couldn't find anything in the logs. What am I missing? Should a docker image be created in some special way? Thanks, Dejan CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail@tttech.com immediately.
Hi Dejan, Were you trying to run docker application inside a VM instance which is managed by OpenStack? I don't quite understand what your use case was, could you articulate a bit more? regards, Yong On 2020/2/4 11:10 PM, Dejan Muhamedagic wrote:
Hi,
I created in openstack an image of the docker type. When an instance of that image starts, the console shows the SeaBIOS version followed by ipxe and the last message is "No bootable device": it looks like as if openstack is trying to create a VM instead of a container. openstack shows the "container_format" of the image as "docker".
The same docker image runs fine on the same controller host when started by hand (docker load, followed by docker run).
I couldn't find anything in the logs.
What am I missing? Should a docker image be created in some special way?
Thanks,
Dejan CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail@tttech.com immediately. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
Hi Yong, On Thu, 2020-02-06 at 09:46 +0800, Yong Hu wrote:
Hi Dejan, Were you trying to run docker application inside a VM instance which is managed by OpenStack?
No. I just tried to launch a docker instance. Are docker instances supposed to run within a VM instance?
I don't quite understand what your use case was, could you articulate a bit more?
I just wanted to create an instance from the image of type docker. There is nothing really special that I tried to do. I looked around for some documentation on how Openstack deploys docker, but couldn't find any information that could help. Thanks, Dejan
regards, Yong
On 2020/2/4 11:10 PM, Dejan Muhamedagic wrote:
Hi,
I created in openstack an image of the docker type. When an instance of that image starts, the console shows the SeaBIOS version followed by ipxe and the last message is "No bootable device": it looks like as if openstack is trying to create a VM instead of a container. openstack shows the "container_format" of the image as "docker".
The same docker image runs fine on the same controller host when started by hand (docker load, followed by docker run).
I couldn't find anything in the logs.
What am I missing? Should a docker image be created in some special way?
Thanks,
Dejan CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail@tttech.com immediately. _______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
_______________________________________________ Starlingx-discuss mailing list Starlingx-discuss@lists.starlingx.io http://lists.starlingx.io/cgi-bin/mailman/listinfo/starlingx-discuss
CONFIDENTIALITY: The contents of this e-mail are confidential and intended only for the above addressee(s). If you are not the intended recipient, or the person responsible for delivering it to the intended recipient, copying or delivering it to anyone else or using it in any unauthorized manner is prohibited and may be unlawful. If you receive this e-mail by mistake, please notify the sender and the systems administrator at straymail@tttech.com immediately.
participants (2)
-
Dejan Muhamedagic
-
Yong Hu