-
Notifications
You must be signed in to change notification settings - Fork 28
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
Error on Windows #28
Comments
I am experiencing this issue as well. |
I am experiencing this issue as well. but i think i successfully build the rails container I don't know much about Rust and the small details of Docker, so I just cloned this repo and tried to modify some code. I ran the container from this repo using the VSCode extension, then executed |
@ruririzal can you make PR? |
For anyone interested, I created a PR for a fix for this a few days ago. |
Same problem here. Could someone accept the PR or teach how to build for windows with this update? |
|
On a Windows 11 Pro PC, I get this error when running the rails-new command:
rails-new -- --devcontainer blog72
(v 0.41)
What's next:
View a summary of image vulnerabilities and recommendations → docker scout quickview
docker: invalid spec: \?\C:\rails:\?\C:\rails: too many colons.
See 'docker run --help'.
thread 'main' panicked at src/main.rs:58:5:
assertion failed: status.success()
note: run with
RUST_BACKTRACE=1
environment variable to display a backtrace<<<
Last line before error above is:
=> => naming to docker.io/library/rails-new-3.3.4-7.2.0
The text was updated successfully, but these errors were encountered: