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

[Issue]: unable to build multiarch docker after dotnet 7.0 using QEMU #9459

Closed
1 task done
sjiampojamarn opened this issue Mar 9, 2023 · 1 comment
Closed
1 task done
Labels
bug Something isn't working stale Stale and will be closed if no activity occurs

Comments

@sjiampojamarn
Copy link

Please describe your bug

I just wondered if anyone else gets a similar issue after dotnet updated to 7.0 in #8686
There is no issue building from a native host -- e.g. arm64 container on arm64 host, amd64 container on amd64 host but unsuccessful for cross-platform. Reported the issue in docker/buildx#1639

Understandably, there is no support for the use-case for QEMU & dotnet specifically but just want to give Jellyfin community here a head-up and if anyone here has a solution / workaround.

Jellyfin Version

10.8.0

if other:

No response

Environment

- OS:
- Virtualization:
- Clients:
- Browser:
- FFmpeg Version:
- Playback Method:
- Hardware Acceleration:
- Plugins:
- Reverse Proxy:
- Base URL:
- Networking:
- Storage:

Jellyfin logs

No response

FFmpeg logs

No response

Please attach any browser or client logs here

No response

Please attach any screenshots here

No response

Code of Conduct

  • I agree to follow this project's Code of Conduct
@sjiampojamarn sjiampojamarn added the bug Something isn't working label Mar 9, 2023
@jellyfin-bot
Copy link
Contributor

This issue has gone 120 days without comment. To avoid abandoned issues, it will be closed in 21 days if there are no new comments.

If you're the original submitter of this issue, please comment confirming if this issue still affects you in the latest release or master branch, or close the issue if it has been fixed. If you're another user also affected by this bug, please comment confirming so. Either action will remove the stale label.

This bot exists to prevent issues from becoming stale and forgotten. Jellyfin is always moving forward, and bugs are often fixed as side effects of other changes. We therefore ask that bug report authors remain vigilant about their issues to ensure they are closed if fixed, or re-confirmed - perhaps with fresh logs or reproduction examples - regularly. If you have any questions you can reach us on Matrix or Social Media.

@jellyfin-bot jellyfin-bot added the stale Stale and will be closed if no activity occurs label Jul 8, 2023
@jellyfin-bot jellyfin-bot closed this as not planned Won't fix, can't repro, duplicate, stale Jul 30, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working stale Stale and will be closed if no activity occurs
Projects
None yet
Development

No branches or pull requests

2 participants