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

[Question]: Truenas Network support/ limitations #543

Closed
2 tasks done
d22b opened this issue May 27, 2024 · 6 comments
Closed
2 tasks done

[Question]: Truenas Network support/ limitations #543

d22b opened this issue May 27, 2024 · 6 comments
Labels
question Further information is requested

Comments

@d22b
Copy link

d22b commented May 27, 2024

Is your question not already answered in the FAQ?

  • I made sure the question is not listed in the FAQ.

Is this a general question and not a technical issue?

  • I am sure my question is not about a technical issue.

Question

Thanks to your project i was able to run this container on a truenas installation and access it via RDP. Unfortunately there are a few limitations in truenas apps and its lack to provide/edit the compose file directly in the app section, i try to work around.

  1. I would like to increase CPU/RAM --> solved by using an modified container
  2. I really want to bridge the container network to my truenas network. Is there an argument i can hardcode into the dockerfile or at least kubernetes file?

With standard network, the container has access to the internet. If i am adding an external Interface (node interface) via truenas app config i can see that it will be applied to the container but within windows this is not the case. Also the Internet connect doesnt work anymore.

@d22b d22b added the question Further information is requested label May 27, 2024
@kroese
Copy link
Contributor

kroese commented May 27, 2024

@d22b For the CPU/RAM limits, you just need to add "Container Environment Variables", see https://github.com/dockur/windows#how-do-i-increase-the-amount-of-cpu-or-ram

For the network, you can enable DHCP variable, and configure the container as seen in these screenshots:

vdsm/virtual-dsm#687 (comment)

and

vdsm/virtual-dsm#687 (comment)

if you follow the steps from that user, it should work!

@d22b
Copy link
Author

d22b commented May 27, 2024

Yes! This will work.

VM_NET_DEV will replace (in my case) the standard adapter. For the value, i had to put in "net1" instead of "eth0" you can have a look in the kubernetes history and it will tell you which interface are beeing added. Maybe we should add these info to the truenas installation procedure.

Thanks again for your support!

@kroese
Copy link
Contributor

kroese commented May 27, 2024

@d22b I am building a new version where it always prefers net1 and net2 over eth0 when they are available, so this step to modify VM_NET_DEV will not be necessary anymore in this new version. For the other steps, maybe you can place screenshots here to help other people using TrueNAS.

@d22b
Copy link
Author

d22b commented May 27, 2024

Yes, i will do that.

Ultimately i have two issues left: USB & GPU passtrough. I followed (and still not finished) carefully #22 but it seems more tricky especially in truenas, to pass an nvidia gpu to the container. I mean practically it work. Jellyfin, plex etc. all of them are able to consume the gpu. It is a matter of config. But step by step.

Any advises for USB passing by env. variable?

@kroese
Copy link
Contributor

kroese commented May 27, 2024

@d22b
Copy link
Author

d22b commented May 30, 2024

No Luck here. I tried to add those parameters to composer.yaml. But the USB Device (CDROM) are not showing up:

services:
windows:
image: windows
container_name: windows
environment:
VERSION: "win11"
RAM_SIZE: "8G"
CPU_CORES: "4"
DHCP: "Y"
ARGUMENTS: "-device usb-host,vendorid=0x174c,productid=0x55aa"
devices:
- /dev/kvm
- /dev/vhost-net
- /dev/bus/usb
device_cgroup_rules:
- 'c : rwm'
cap_add:
- NET_ADMIN
ports:
- 8006:8006
- 3389:3389/tcp
- 3389:3389/udp
stop_grace_period: 2m

@kroese kroese closed this as completed Oct 1, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
question Further information is requested
Projects
None yet
Development

No branches or pull requests

2 participants