© CCFOUND sp. z o.o. sp.k.

KASM Workspace доступ к локальной сети через браузер

Кто-нибудь из вас, возможно, использовал KASM Workspace и имеет техническое знание об этом решении?

Я установил его на Qnap'е и оно работает очень хорошо. Я запустил постоянные сеансы и хорошо стримит браузеры. Однако я не могу дать браузеру доступ к сетевым ресурсам. Когда я пытаюсь сохранить что-либо локально, вижу только ресурсы контейнера (каталог Desktop, Downloads и Uploads). Кажется, что ключом может быть здесь volume mapping, но это очевидно превосходит мои возможности.

Кто-нибудь из вас, возможно, использовал KASM Workspace и имеет техническое знание об этом решении?

Я установил его на Qnap'е и оно работает очень хорошо. Я запустил постоянные сеансы и хорошо стримит браузеры. Однако я не могу дать браузеру доступ к сетевым ресурсам. Когда я пытаюсь сохранить что-либо локально, вижу только ресурсы контейнера (каталог Desktop, Downloads и Uploads). Кажется, что ключом может быть здесь volume mapping, но это очевидно превосходит мои возможности.

Show original content

0 users upvote it!

3 answers


Krupaela
Unfortunately no.
Unfortunately no.

Machine translated


MarekRoszak
KASM Workspace is a solution for virtualizing web browsers. From what I understand, you want to access network resources in your browser. According to the KASM Workspace documentation, to access network resources in the browser, you need to configure the KASM Workspace agent to have network access. This can be done, for example, by setting the appropriate rules in the firewall¹. Regarding the issue of volume mapping, it is indeed crucial for accessing files and folders on Qnap. In the case of KASM Workspace, to access files and folders on Qnap, you need to configure volume mapping in the docker-compose.yml file¹. I hope I helped!
KASM Workspace is a solution for virtualizing web browsers. From what I understand, you want to access network resources in your browser. According to the KASM Workspace documentation, to access network resources in the browser, you need to configure the KASM Workspace agent to have network access. This can be done, for example, by setting the appropriate rules in the firewall¹. Regarding the issue of volume mapping, it is indeed crucial for accessing files and folders on Qnap. In the case of KASM Workspace, to access files and folders on Qnap, you need to configure volume mapping in the docker-compose.yml file¹. I hope I helped!

Machine translated


OpenAI BOT
My advice regarding your problem with browser access to network resources in KASM Workspace is as follows: Try mapping the appropriate directories or folders on your Qnap as a volume for the KASM Workspace container. This will move the local resources to the container and you will be able to access them from the browser. To do this, you can use the "volume mapping" option in the KASM Workspace container configuration. In this section, you can tell the container which local resources should be attached as volumes. For example, if you want to access your "Documents" directory on Qnap, you can map this directory as a volume. Below is an example HTML code: html Try mapping the appropriate directories or folders on your Qnap as a volume for the KASM Workspace container. To do this, configure the "volume mapping" section in KASM Workspace, which specifies which local resources should be attached as volumes. For example, map your "Documents" directory as a volume. I hope this helps you solve the problem with accessing network resources in KASM Workspace. If you have any more questions, I'll be happy to help!
My advice regarding your problem with browser access to network resources in KASM Workspace is as follows: Try mapping the appropriate directories or folders on your Qnap as a volume for the KASM Workspace container. This will move the local resources to the container and you will be able to access them from the browser. To do this, you can use the "volume mapping" option in the KASM Workspace container configuration. In this section, you can tell the container which local resources should be attached as volumes. For example, if you want to access your "Documents" directory on Qnap, you can map this directory as a volume. Below is an example HTML code: html Try mapping the appropriate directories or folders on your Qnap as a volume for the KASM Workspace container. To do this, configure the "volume mapping" section in KASM Workspace, which specifies which local resources should be attached as volumes. For example, map your "Documents" directory as a volume. I hope this helps you solve the problem with accessing network resources in KASM Workspace. If you have any more questions, I'll be happy to help!

Machine translated