-
-
Notifications
You must be signed in to change notification settings - Fork 190
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] bind source does not exist #131
Comments
Hello @MattPlayGamez, I would have some additional information to help you.
The exegol wrapper tries to bind the path to the resources (ˋexegol-resourcesˋ), but the path is invalid. Also, your problem comes from wrapper, I think this issue should be moved to the other exegol repo : https://github.com/ThePorgs/Exegol (cc @ShutdownRepo) |
Hello @MattPlayGamez |
Hi @Dramelac and @QU35T-code, I have ubuntu (WSL) installed. |
Hi @MattPlayGamez, Is this bug still exist with the current version of Exegol (4.2.1) ? |
The problem seems to be related to your WSL installation and not directly to Exegol. The easiest way is that you open a ticket on the Discord for better interaction to fix your problem. |
Hi,
Sorry that I wasn't answerig previously. I had completly forgotten about it.
I'll look later today (and set this email as unread so I Cant forget about
it).
I will reinstall it then
Op za 13 mei 2023 12:39 schreef Dramelac ***@***.***>:
… Hi @MattPlayGamez <https://github.com/MattPlayGamez>,
Is this bug still exist with the current version of Exegol (4.2.1) ?
—
Reply to this email directly, view it on GitHub
<#131 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AOZHOEXUYWYICV33FYM6QW3XF5QEJANCNFSM6AAAAAAUCJGXAI>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
No, The issue has been resolved
[image: Mailtrack]
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&>
Sender
notified by
Mailtrack
<https://mailtrack.io?utm_source=gmail&utm_medium=signature&utm_campaign=signaturevirality11&>
05/22/23,
05:20:05 PM
Op za 13 mei 2023 om 13:30 schreef MattPlayGamez ***@***.***>:
… Hi,
Sorry that I wasn't answerig previously. I had completly forgotten about
it.
I'll look later today (and set this email as unread so I Cant forget about
it).
I will reinstall it then
Op za 13 mei 2023 12:39 schreef Dramelac ***@***.***>:
> Hi @MattPlayGamez <https://github.com/MattPlayGamez>,
>
> Is this bug still exist with the current version of Exegol (4.2.1) ?
>
> —
> Reply to this email directly, view it on GitHub
> <#131 (comment)>,
> or unsubscribe
> <https://github.com/notifications/unsubscribe-auth/AOZHOEXUYWYICV33FYM6QW3XF5QEJANCNFSM6AAAAAAUCJGXAI>
> .
> You are receiving this because you were mentioned.Message ID:
> ***@***.***>
>
--
si vous avez des questions, envoyez-les à mon email
***@***.***>
cordialement Mathys
heeft u nog vragen zend het dan naar mijn email ***@***.***>
met vriendelijke groet Mathys
|
Describe the bug
Hi,
I got an error (see below). I didn't change anything since previous time and I'm a bit suprised
`
PS C:\Users\mathy> exegol start default full -cwd --disable-shared-timezones --disable-shared-network --vpn D:\Exegol\Docker.ovpn
C:\Users\mathy\AppData\Local\Programs\Python\Python310\lib\site-packages\paramiko\transport.py:178: CryptographyDeprecationWarning: Blowfish has been deprecated
'class': algorithms.Blowfish,
[] Exegol is currently in version v4.1.0
[] Exegol Discord serv.: https://discord.gg/cXThyp7D6P
[] Exegol documentation: https://exegol.rtfd.io/
[+] We thank Capgemini for supporting the project (helping with dev) 🙏
[+] We thank HackTheBox for sponsoring the multi-arch support 💚
[] Starting exegol
[*] Arguments supplied with the command, skipping interactive mode
<3>WSL (245) ERROR: UtilTranslatePathList:2671: Failed to translate D:\IntelliJ\bin
<3>WSL (248) ERROR: UtilTranslatePathList:2671: Failed to translate D:\IntelliJ\bin
<3>WSL (18111) ERROR: UtilTranslatePathList:2671: Failed to translate D:\IntelliJ\bin
⭐ Container summary
┌──────────────────┬──────────────────────────────────────────────────────────────┐
│ Name │ default │
│ Image │ full - v.3.0.0 (Up to date) │
├──────────────────┼──────────────────────────────────────────────────────────────┤
│ GUI │ On ✔ │
│ Network │ bridge with VPN │
│ Timezone │ Off 🪓 │
│ Exegol resources │ On ✔ (/opt/resources) │
│ My resources │ On ✔ (/opt/my-resources) │
│ Shell logging │ Off 🪓 │
│ VPN │ Docker.ovpn │
│ Privileged │ Off ✔ │
│ Capabilities │ NET_ADMIN │
│ Workspace │ C:\Users\mathy (/workspace) │
│ Devices │ /dev/net/tun │
│ Volumes │ D:\Exegol\Docker.ovpn ➡ /.exegol/vpn/config/client.ovpn (RO) │
│ Systctls │ net.ipv6.conf.all.disable_ipv6 = 0 │
└──────────────────┴──────────────────────────────────────────────────────────────┘
[*] Creating new exegol container
[-] invalid mount config for type "bind": bind source path does not exist:
/run/desktop/mnt/host/d/Exegol/exegol-resources
[!] Error while creating exegol container. Exiting.
PS C:\Users\mathy>
`
Steps To Reproduce
1: Start a container (with this command:
exegol start default full -cwd --disable-shared-timezones --disable-shared-network --vpn D:\Exegol\Docker.ovpn
)2. Get this error
[-] invalid mount config for type "bind": bind source path does not exist: /run/desktop/mnt/host/d/Exegol/exegol-resources [!] Error while creating exegol container. Exiting.
Exegol Wrapper Version
Exegol container information
Exception
No response
Additional context
No response
Anything else?
No response
The text was updated successfully, but these errors were encountered: