Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] failed to create shim task #46

Closed
1 task done
jon4sweber opened this issue Jan 9, 2024 · 6 comments
Closed
1 task done

[BUG] failed to create shim task #46

jon4sweber opened this issue Jan 9, 2024 · 6 comments

Comments

@jon4sweber
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Kasm workspaces do not start due to an unknown Error.

Expected Behavior

No response

Steps To Reproduce

everytime when trying to start a kasm workspace

Environment

- OS: alpine 3.18
- How docker service was installed:

CPU architecture

x86-64

Docker creation

---
version: "2.1"
services:
  kasm:
    image: lscr.io/linuxserver/kasm:latest
    container_name: kasm
    privileged: true
    environment:
      - KASM_PORT=443
      - DOCKER_HUB_USERNAME=USER #optional
      - DOCKER_HUB_PASSWORD=PASS #optional
      - DOCKER_MTU=1500 #optional
    volumes:
      - /path/to/data:/opt
      - /path/to/profiles:/profiles #optional
      - /dev/input:/dev/input #optional
      - /run/udev/data:/run/udev/data #optional
    ports:
      - 3000:3000
      - 443:443
    restart: unless-stopped

Container logs

(Exception creating Kasm: Traceback (most recent call last):
  File "docker/api/client.py", line 268, in _raise_for_status
  File "requests/models.py", line 1021, in raise_for_status
requests.exceptions.HTTPError: 500 Server Error: Internal Server Error for url: http+docker://localhost/v1.43/containers/bc751be32625b0279093a617838490b287d2e057f8268b072590e0ddf1c04072/start

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "__init__.py", line 539, in post
  File "provision.py", line 1547, in provision
  File "provision.py", line 1539, in provision
  File "docker/models/containers.py", line 818, in run
  File "docker/models/containers.py", line 404, in start
  File "docker/utils/decorators.py", line 19, in wrapped
  File "docker/api/container.py", line 1111, in start
  File "docker/api/client.py", line 270, in _raise_for_status
  File "docker/errors.py", line 31, in create_api_error_from_http_exception
docker.errors.APIError: 500 Server Error for http+docker://localhost/v1.43/containers/bc751be32625b0279093a617838490b287d2e057f8268b072590e0ddf1c04072/start: Internal Server Error ("failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: unable to apply cgroup configuration: cannot enter cgroupv2 "/sys/fs/cgroup/docker" with domain controllers -- it is in threaded mode: unknown")
Copy link

github-actions bot commented Jan 9, 2024

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

@thelamer
Copy link
Member

I have never tested DinD like this on an Alpine host, the error seems to indicate that Docker is not running inside of the container properly. Do other DinD container work properly on an Alpine host? (keep in mind this one is Jammy based as well)

@jon4sweber
Copy link
Author

Thanks for the reply!
I do have a jupyterlab, swag, freecad and webtop container running on the same host. The deployment with kasm has worked before. unfortunately i cannot specify if an alpine or kasm update broke it.

@thelamer
Copy link
Member

When I say DinD container I am referring to stuff like this https://hub.docker.com/_/docker where you run a container with it's own docker runtime in privileged mode.

@LinuxServer-CI
Copy link
Collaborator

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

@LinuxServer-CI LinuxServer-CI closed this as not planned Won't fix, can't repro, duplicate, stale Apr 18, 2024
@LinuxServer-CI LinuxServer-CI moved this from Issues to Done in Issue & PR Tracker Apr 18, 2024
Copy link

This issue is locked due to inactivity

@github-actions github-actions bot locked as resolved and limited conversation to collaborators May 18, 2024
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
Archived in project
Development

No branches or pull requests

3 participants