# Unable to run linux container

**URL:** <https://forum.opennebula.io/t/unable-to-run-linux-container/10469>\
**Category:** Product Support\
**Created:** [April 12, 2022, 11:37am UTC](https://forum.opennebula.io/t/unable-to-run-linux-container/10469 "2022-04-12T11:37:55Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![DoctorZhivago](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@DoctorZhivago](https://forum.opennebula.io/u/DoctorZhivago)\
**Post date:** [April 12, 2022, 11:37am UTC](https://forum.opennebula.io/t/unable-to-run-linux-container/10469/1 "2022-04-12T11:37:55Z")

</div>

Hello everyone. I use firecracker-hypervisor, and downloaded an ubuntu-image from the built-in appstore. The container boots up, but I’ve no access to it. So I can’t show the console output.  
If I want to add a network-interface to access the system, I get:

> > >

**Driver Error**  
Tue Apr 12 11:13:43 2022: DEPLOY: DEBUG: deploy: Creating VM: ‘screen -dmS one-76 sudo -n jailer --id one-76 --node 1 --exec-file /usr/bin/firecracker --uid 9869 --gid 9869 – --config-file deployment.file’ MicroVM process did not start. ExitCode: 255  
\<\<\<  
In menu “Storage” → “Images”, I get “Status: Error”

Do you have any hints how to troubleshoot this problem?  
I tried it with Nginx and followed instructions in this Opennebula-video:

> **[OpenNebula + Firecracker: Building the Future of On-Premises Serverless...](https://opennebula.io/blog/development/opennebula-firecracker-building-the-future-of-on-premises-serverless-computing/)**
>
> Firecracker is a new open source virtualization technology—widely used by AWS as part of its Fargate and Lambda services⁠—especially designed for creating and

It also doesn’t work  
Because I’m completely new to this container subject, please keep it simple 🙂

Thank you

**Versions of the related components and OS (frontend, hypervisors, VMs):**  
Opennebula-Testsystem: Just one node.  
Opennebula 6.2  
Hypervisor: Firecracker  
Ubuntu-impish - LXD  
Services installed: opennebula, opennebula-flow, opennebula-gate, opennebula-sunstone, opennebula-kvm, opennebula-firecracker, opennebula-fireedge

**Steps to reproduce:**  
Attach NIC or network-connectivity to guest, and it doesn’t boot up.

**Current results:**  
Booterror, Failure

**Expected results:**

---

<div class="post-metadata">

**Author:** ![dclavijo](https://yyz1.discourse-cdn.com/flex031/user_avatar/forum.opennebula.io/dclavijo/32/5265_2.png) [@dclavijo](https://forum.opennebula.io/u/dclavijo)\
**Post date:** [April 12, 2022, 2:00pm UTC](https://forum.opennebula.io/t/unable-to-run-linux-container/10469/2 "2022-04-12T14:00:03Z")

</div>

In order to correctly create a firecracker host, please check [the official guide](https://docs.opennebula.io/6.2/open_cluster_deployment/firecracker_node/overview.html). It is possible you are missing [this step](https://docs.opennebula.io/6.2/open_cluster_deployment/firecracker_node/firecracker_driver.html#networking) required for an operational networking for the microvms. Note that firecracker creates microvms, not Linux Containers, for those you need either the LXC/LXD drivers.

---

<div class="post-metadata">

**Author:** ![DoctorZhivago](https://avatars.discourse-cdn.com/v4/letter/d/bb73d2/32.png) [@DoctorZhivago](https://forum.opennebula.io/u/DoctorZhivago)\
**Post date:** [May 11, 2022, 3:02pm UTC](https://forum.opennebula.io/t/unable-to-run-linux-container/10469/3 "2022-05-11T15:02:01Z")

</div>

Can be closed