failed to create coreclr, hresult: "0x8007ff02"

danieledwardgeorgehitchcock commented 2 years ago

Expected Behavior

Service container gets pulled and starts successfully

Current Behavior

Service fails to run with error failed to create coreclr, hresult: 0x8007ff02

Steps to Reproduce

1.Pull the image with the below docker compose file 2.Attempt to start the container 3.Monitor container logs

From a bit of googling, it seems that this is due to the process not having any available memory. I have tried adding cap_add: IPC_LOCK in my docker compose file to resolve the issue, and have also tried manually building the container with libcap2-bin included and setcap cap_ipc_lock=+eip /opt/ombi/Ombi added to the run script.

I have tried this on a fresh restart of my machine and nothing seems to work.

Environment

OS: Ubuntu 20.04 LTS CPU architecture: x86_64 How docker service was installed:

From Linux Server container repository using docker compose

Command used to create docker container (run/create/compose/screenshot)

Docker compose:

  ombi:
    hostname: ombi
    image: ghcr.io/linuxserver/ombi:latest
    container_name: ombi
    restart: unless-stopped
    depends_on:
      - traefik
      - mariadb
    volumes:
      - type: volume
        source: ombi-config
        target: /config
        read_only: False
    networks:
      - reverse_proxy
      - database
    environment:
      - PUID=${PUID}
      - PGID=${PGID}
      - TZ=${TZ}
    labels:
      traefik.enable: True
      traefik.backend: ombi
      traefik.frontend.rule: "Host:ombi.${DOMAINNAME}; AddPrefix: /ombi"
      traefik.port: 3579
      traefik.docker.network: docker_reverse_proxy

Service was brought up using docker-compose -f docker-compose.yml up -d

Docker logs

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing... 
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 10-adduser: executing... 
usermod: no changes
-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \ 
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/
Brought to you by linuxserver.io
-------------------------------------
To support the app dev(s) visit:
Ombi - Patreon: https://patreon.com/tidusjar
Ombi - PayPal: https://paypal.me/PlexRequestsNet
To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
User uid:    1000
User gid:    999
-------------------------------------
[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
[cont-init.d] 30-config: exited 0.
[cont-init.d] 90-custom-folders: executing... 
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-scripts: executing... 
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Failed to create CoreCLR, HRESULT: 0x8007FF02

github-actions[bot] commented 2 years ago

Thanks for opening your first issue here! Be sure to follow the bug or feature issue templates!

aptalca commented 2 years ago

Is this in a VM or bare metal? https://github.com/dotnet/runtime/issues/44417#issuecomment-855288407

danieledwardgeorgehitchcock commented 2 years ago

This is a bare metal machine (16GB RAM) pretty much just running other docker containers - no other virtualisation - I saw that thread, this is why I assumed that the container didn't have any available memory and added the IPC_LOCK

aptalca commented 2 years ago

What's surprising to me is this comment there: We use different HRESULT codes for different failure locations and the problem specific to 0x8007FF02 was never observed on anything else than macOS.

aptalca commented 2 years ago

Can you repull the latest image (delete the old one first to make sure) and create a fresh test container with just docker run -d --rm --name test -p 3579:3579 lscr.io/linuxserver/ombi and then check the logs and try to access at http://LOCALIP:3579 ?

danieledwardgeorgehitchcock commented 2 years ago

I am getting the same message in the logs, and I am unable to connect through into the Ombi WebUI (refused to connect)

aptalca commented 2 years ago

I just tested on an x86_64 machine with ubuntu 20.04.3 and can't reproduce

How did you install docker? From the ubuntu repo or from the official docker repo?

danieledwardgeorgehitchcock commented 2 years ago

The official docker repo. I used to have Ombi running about a year ago - it wasn’t until I came to use it recently that I’d realised it had broken.

The only thing that I have changed since, is relocating my docker data folder to an ssd?

github-actions[bot] commented 2 years ago

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

hugalafutro commented 2 years ago

I have just run into similar issue (different error code) on a ubuntu x64 vm after pulling latest image about five mins ago (I'm too stupid to figure out the commit number or w/e, I just update every few days to latest, so it happens in the version that was latest at the time of writing this, but no on the version that was latest before that)

edit: ombi was running for over a year without issue before that, although I only used it few times a month so maybe it wasn't working every now and then.

ombi  | -------------------------------------
ombi  |           _         ()
ombi  |          | |  ___   _    __
ombi  |          | | / __| | |  /  \
ombi  |          | | \__ \ | | | () |
ombi  |          |_| |___/ |_|  \__/
ombi  |
ombi  |
ombi  | Brought to you by linuxserver.io
ombi  | -------------------------------------
ombi  |
ombi  | To support the app dev(s) visit:
ombi  | Ombi - Patreon: https://patreon.com/tidusjar
ombi  | Ombi - PayPal: https://paypal.me/PlexRequestsNet
ombi  |
ombi  | To support LSIO projects visit:
ombi  | https://www.linuxserver.io/donate/
ombi  | -------------------------------------
ombi  | GID/UID
ombi  | -------------------------------------
ombi  |
ombi  | User uid:    1000
ombi  | User gid:    1000
ombi  | -------------------------------------
ombi  |
ombi  | [cont-init.d] 10-adduser: exited 0.
ombi  | [cont-init.d] 30-config: executing...
ombi  | [cont-init.d] 30-config: exited 0.
ombi  | [cont-init.d] 90-custom-folders: executing...
ombi  | [cont-init.d] 90-custom-folders: exited 0.
ombi  | [cont-init.d] 99-custom-scripts: executing...
ombi  | [custom-init] no custom files found exiting...
ombi  | [cont-init.d] 99-custom-scripts: exited 0.
ombi  | [cont-init.d] done.
ombi  | [services.d] starting services
ombi  | [services.d] done.
ombi  | Failed to create CoreCLR, HRESULT: 0x80070008
ombi  | Failed to create CoreCLR, HRESULT: 0x80070008
ombi  | Failed to create CoreCLR, HRESULT: 0x80070008
ombi  | Failed to create CoreCLR, HRESULT: 0x80070008

the message repeats inifnitely.

alexmarsaudon commented 2 years ago

+1 for the above - latest image, ubuntu 20.04 lts, no other changes to my environment

jorgentol commented 2 years ago

I have the same issue now. latest build

zkhcohen commented 2 years ago

Same issue. Was this build tested?

Roxedus commented 2 years ago

Same issue. Was this build tested?

Yes. https://ci-tests.linuxserver.io/linuxserver/ombi/latest/index.html

Roxedus commented 2 years ago

Please provide the information asked for in the template

aptalca commented 2 years ago

^^ that's develop and here's stable (latest): https://ci-tests.linuxserver.io/linuxserver/ombi/v4.16.12-ls120/index.html

alexmarsaudon commented 2 years ago

Expected Behavior

Container should start gracefully

Current Behavior

Steps to Reproduce

Including mention of my proxy config since the other reporter mentioned running behind traefik -

For me, I believe the following would be required to recreate my config:
Ubuntu 20.04.4 LTS x64. Docker installed.
Run NGINX container docker run -d -p 80:80 -p 443:443 --name nginx-proxy -e DEFAULT_HOST=subdomain.domain.com -v /data/nginx/certs:/etc/nginx/certs:ro -v /data/nginx/vhost.d:/etc/nginx/vhost.d -v /data/nginx/html:/usr/share/nginx/html -v /var/run/docker.sock:/tmp/docker.sock:ro --restart=unless-stopped jwilder/nginx-proxy:latest
Run acme-companion container - docker run -d --name letsencrypt --volumes-from nginx-proxy --volume /var/run/docker.sock:/var/run/docker.sock:ro -v /data/nginx/certs:/etc/nginx/certs:rw --volume acme:/etc/acme.sh --env "DEFAULT_EMAIL=alex@domain.com" --restart=unless-stopped nginxproxy/acme-companion
Run the ombi container - docker run -d --name=ombi --restart=unless-stopped -v /data/ombi:/config -e PGID=1000 -e PUID=1000 -p 3579:3579 -e TZ=America/Los_Angeles -v /zfs-media/TV:/TV -v /zfs-media/Music:/music -v /zfs-media/Movies:/movies -e VIRTUAL_HOST=ombi.domain.com,subdomain2.domain.com -e "LETSENCRYPT_HOST=ombi.domain.com,subdomain2.domain.com" -e "LETSENCRYPT_EMAIL=alex@domain.com" linuxserver/ombi

Environment

OS: Ubuntu 20.04 LTS x64 - CPU architecture: x86_64 How docker service was installed:

https://docs.docker.com/engine/install/ubuntu/#install-using-the-repository

Command used to create docker container (run/create/compose/screenshot)

See above - steps to reproduce

Docker logs

`[s6-init] making user provided files available at /var/run/s6/etc...exited 0. [s6-init] ensuring user provided files have correct perms...exited 0. [fix-attrs.d] applying ownership & permissions fixes... [fix-attrs.d] done. [cont-init.d] executing container initialization scripts... [cont-init.d] 01-envfile: executing... [cont-init.d] 01-envfile: exited 0. [cont-init.d] 01-migrations: executing... [migrations] started [migrations] no migrations found [cont-init.d] 01-migrations: exited 0. [cont-init.d] 02-tamper-check: executing... [cont-init.d] 02-tamper-check: exited 0. [cont-init.d] 10-adduser: executing...

      _         ()
     | |  ___   _    __
     | | / __| | |  /  \
     | | \__ \ | | | () |
     |_| |___/ |_|  \__/

Brought to you by linuxserver.io

To support the app dev(s) visit: Ombi - Patreon: https://patreon.com/tidusjar Ombi - PayPal: https://paypal.me/PlexRequestsNet

To support LSIO projects visit: https://www.linuxserver.io/donate/

GID/UID

User uid: 1000 User gid: 1000

[cont-init.d] 10-adduser: exited 0. [cont-init.d] 30-config: executing... [cont-init.d] 30-config: exited 0. [cont-init.d] 90-custom-folders: executing... [cont-init.d] 90-custom-folders: exited 0. [cont-init.d] 99-custom-scripts: executing... [custom-init] no custom files found exiting... [cont-init.d] 99-custom-scripts: exited 0. [cont-init.d] done. [services.d] starting services [services.d] done. Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 Failed to create CoreCLR, HRESULT: 0x80070008 `

martijnmelchers commented 2 years ago

Having the same issue!

j0nnymoe commented 2 years ago

@alexmarsaudon thank you for the detailed issue. To everyone else, saying "having the same issue" with no other information provided is not helpful.

n-i-x commented 2 years ago

I was able to revert to amd64-4.16.11 and it worked again.

Roxedus commented 2 years ago

The original issue is unrelated to what hugalafutro is seeing, and anyone after, it should realistically be a separate issue.

Try raising your ulimits https://github.com/dotnet/sdk/issues/9785#issuecomment-426037916

alexmarsaudon commented 2 years ago

Sorry for the stupid question, but - can you clarify? Adjusting host-side had no impact:

[amarsaudon@pms:~]$ ulimit -n
1024
[amarsaudon@pms:~]$ ulimit -n 4864
[amarsaudon@pms:~]$ ulimit -n
4864
[amarsaudon@pms:~]$ docker stop ombi && docker rm -f ombi
ombi
ombi
[amarsaudon@pms:~]$ docker run -d --name=ombi --restart=unless-stopped -v /data/ombi:/config -e PGID=1000 -e PUID=1000 -p 3579:3579 -e TZ=America/Los_Angeles -v /zfs-media/TV:/TV -v /zfs-media/Music:/music -v /zfs-media/Movies:/movies -e VIRTUAL_HOST=subdomain.domain -e "LETSENCRYPT_HOST=subdomain.domain" -e "LETSENCRYPT_EMAIL=alex@domain.com" linuxserver/ombi && docker logs -f --tail=100 ombi
ce5254650e6c7fd061f9a8849f4e391c1f84b3c4f21b8a361f9b9a017e41ceae
[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01-envfile: executing... 
[cont-init.d] 01-envfile: exited 0.
[cont-init.d] 01-migrations: executing... 
[migrations] started
[migrations] no migrations found
[cont-init.d] 01-migrations: exited 0.
[cont-init.d] 02-tamper-check: executing... 
[cont-init.d] 02-tamper-check: exited 0.
[cont-init.d] 10-adduser: executing... 

-------------------------------------
          _         ()
         | |  ___   _    __
         | | / __| | |  /  \
         | | \__ \ | | | () |
         |_| |___/ |_|  \__/

Brought to you by linuxserver.io
-------------------------------------

To support the app dev(s) visit:
Ombi - Patreon: https://patreon.com/tidusjar
Ombi - PayPal: https://paypal.me/PlexRequestsNet

To support LSIO projects visit:
https://www.linuxserver.io/donate/
-------------------------------------
GID/UID
-------------------------------------

User uid:    1000
User gid:    1000
-------------------------------------

[cont-init.d] 10-adduser: exited 0.
[cont-init.d] 30-config: executing... 
[cont-init.d] 30-config: exited 0.
[cont-init.d] 90-custom-folders: executing... 
[cont-init.d] 90-custom-folders: exited 0.
[cont-init.d] 99-custom-scripts: executing... 
[custom-init] no custom files found exiting...
[cont-init.d] 99-custom-scripts: exited 0.
[cont-init.d] done.
[services.d] starting services
[services.d] done.
Failed to create CoreCLR, HRESULT: 0x80070008
Failed to create CoreCLR, HRESULT: 0x80070008
Failed to create CoreCLR, HRESULT: 0x80070008
Failed to create CoreCLR, HRESULT: 0x80070008
^C
[amarsaudon@pms:~]$

Adjusting within the container doesn't seem to be permitted:

root@ce5254650e6c:/# ulimit -n
1048576
root@ce5254650e6c:/# ulimit -n 2048576
bash: ulimit: open files: cannot modify limit: Operation not permitted
root@ce5254650e6c:/# ^C
root@ce5254650e6c:/#

hollanbm commented 2 years ago

The original issue is unrelated to what hugalafutro is seeing, and anyone after, it should realistically be a separate issue.

Try raising your ulimits dotnet/sdk#9785 (comment)

I upped my system ulimit, to 4096 and restarted the docker daemon. No change. I had to downgrade to the previous version

I was able to revert to amd64-4.16.11 and it worked again.

Thanks, this solved the issue for me (for now) -- I'll check back in a few days

alexmarsaudon commented 2 years ago

Anyone else have their linuxserver hydra2 container eat it too? Now 502'ing, scrolling a different error:

Logging wrapper output to /config/logs/wrapper.log 2022-05-05 06:35:44,876 ERROR - Unable to determine java version; make sure Java is installed and callable. Error message: Unable to determine java version from string [0.005s][warning][os,thread] Failed to start thread - pthread_create failed (EPERM) for attributes: stacksize: 1024k, guardsize: 4k, detached.

j0nnymoe commented 2 years ago

This is the ombi repo, not nzbhydra.

alexmarsaudon commented 2 years ago

Shoulda been more clear, I am only asking since it has what appears to be a similar failure to what I experienced here with Ombi. For both to fail in the same week after update, and both be citing similar issues ( ulimits vs pthread_create failed ) seems a lot like this issue will boil down to something common that was changed with those two containers in this most recent update that mine (and others) docker hosts aren't tolerating. Was just hoping mention of this would also serve as a clue.

mnkhouri commented 2 years ago

It appears this is addressed in https://docs.linuxserver.io/faq#jammy

I found that via the issue linked by @alexmarsaudon (thanks for linking!) https://github.com/linuxserver/docker-nzbhydra2/issues/20#issuecomment-1118863061

alexmarsaudon commented 2 years ago

Yea bigtime thanks to @j0nnymoe , coulda sworn I was on current docker but I guess I was on 19.x. Derp. Fixed it for me.

hollanbm commented 2 years ago

It appears this is addressed in https://docs.linuxserver.io/faq#jammy

Thank you!

this was my issue. I had no idea I was using v19

hbh7 commented 2 years ago

I had the same issue, and apparently my version was 20.10.9, so I was just barely below the threshold lol. Thanks @mnkhouri !

github-actions[bot] commented 2 years ago

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

github-actions[bot] commented 1 year ago

This issue is locked due to inactivity

linuxserver / docker-ombi