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

[Setup] Show warning when running on docker for Win using JSON backend #2989

Open
orels1 opened this issue Sep 8, 2019 · 1 comment
Open
Labels
Category: Core - API - Config This is related to the `redbot.core.config` module and `redbot.core.drivers` package. Category: Core - Command-line Interfaces This is related to Red's CLIs (redbot, redbot-launcher, redbot-setup). Status: Needs Discussion Needs more discussion. Type: Bug Unexpected behavior, result, or exception. In case of PRs, it is a fix for the foregoing.

Comments

@orels1
Copy link
Member

orels1 commented Sep 8, 2019

Other bugs

What were you trying to do?

Run red through an archlinux container on windows 10 host using JSON as a backend using existing data from a previous installation

What were you expecting to happen?

It to work

What actually happened?

It crashed and burned with a cryptic error

image

How can we reproduce this issue?

Run the bot under archlinux/base on a windows host using a volume connected to Windows FS as the bot data path

Additional info

So after talking with @mikeshardmind i tried using a second docker-specific volume as the bot data path to work around Windows being Windows.

Basically the install process looked like this then:

  • docker volume create the actual volume i'll be using
  • docker run connecting both newely created volume and a path to a host machine (i used -v <localPath>:<containerPath> to mount)
  • install all the things inside the container
  • install the bot and do a first launch
  • shut down the bot and copy over the data from the host-connected volume into the docker-specific volume
  • launch the bot, now it should work fine

Hope this info helps, sharing since Sinbad asked me to, would love to see some warning about windows issues in the docs or instead of that crashlog

@Flame442 Flame442 added the Type: Bug Unexpected behavior, result, or exception. In case of PRs, it is a fix for the foregoing. label Sep 24, 2019
@Jackenmen Jackenmen added Category: Bot Core Status: Needs Triage This has not been labeled or discussed for handling yet. labels Jan 16, 2020
@Drapersniper Drapersniper added Status: Needs Discussion Needs more discussion. and removed Status: Needs Triage This has not been labeled or discussed for handling yet. labels Jun 26, 2020
@mikeshardmind
Copy link
Contributor

I can repro this on WSL version 1, but not with WSL version 2. Given that and what I observed about the failure condition, I don't think this is something we can fix, but it could be documented that WSL v2 is needed for WSL users.

@Jackenmen Jackenmen added Category: Core - API - Config This is related to the `redbot.core.config` module and `redbot.core.drivers` package. Category: Core - Command-line Interfaces This is related to Red's CLIs (redbot, redbot-launcher, redbot-setup). and removed Category: Bot Core labels Feb 12, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Category: Core - API - Config This is related to the `redbot.core.config` module and `redbot.core.drivers` package. Category: Core - Command-line Interfaces This is related to Red's CLIs (redbot, redbot-launcher, redbot-setup). Status: Needs Discussion Needs more discussion. Type: Bug Unexpected behavior, result, or exception. In case of PRs, it is a fix for the foregoing.
Projects
None yet
Development

No branches or pull requests

5 participants