Devcontainer does not have access to `/dev/kvm` after resuming a devcontainer in codespaces

[dblnz]

What happened?

After resuming a previously created devcontainer in github Codespaces, the user does not have access to /dev/kvm

What did you expect to happen?

It is expected that the user has access to /dev/kvm

Steps to reproduce the behavior

1. Create new codespace in Github
2. Check access to /dev/kvm - has access
3. Stop the codespace
4. Start the codespace
5. The user does not have access to /dev/kvm anymore

Hyperlight Version

0.1.0

OS version

On Linux:
$ cat /etc/os-release
# paste output here

$ uname -a
# paste output here

On Windows:
C:\> cmd /c ver
# paste output here

Additional Information

By running a chown/chmod command to change permissions for the running user, the issue is solved.
This needs to be done every time the container is closed.

[myadav27]

I tested on the my codespaces and adding a line in .devcontainer/devcontainer.json, solved my problem

  // Runs every time container is started/restarted
  "postStartCommand": "sudo chmod 666 /dev/kvm",

Complete file:

{
  "name": "Hyperlight",

  "image": "ghcr.io/hyperlight-dev/hyperlight-devcontainer:latest",

  "containerUser": "vscode",
  "containerEnv": {
    "DEVICE": "/dev/kvm",
    "REMOTE_USER": "vscode",
    "REMOTE_GROUP": "vscode"
  },

  "runArgs": [
    "--device=/dev/kvm"
  ],

  // Runs only once, when container is created
  "postCreateCommand": "bash .devcontainer/setup.sh",

  // Runs every time container is started/restarted
  "postStartCommand": "sudo chmod 666 /dev/kvm",

  "customizations": {
    "vscode": {
      "extensions": [
        "ms-vscode.cmake-tools",
        "rust-lang.rust-analyzer",
        "vadimcn.vscode-lldb"
      ],
      "settings": {
        "rust-analyzer.rustfmt.extraArgs": [
          "+nightly"
        ]
      }
    }
  }
}

[myadav27]

Please refer #326 for the fix

[ludfjig]

Closing as this was fixed in #326