-
Notifications
You must be signed in to change notification settings - Fork 38
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
unable to install conan as mentioned in this step. I get below error #82
Comments
Hello Admin,
|
i installed latest stable docker on all those OSs |
Hi, I got the same issue on my Debian 11 VM. I'm trying to fix it. |
@chiragshah2406 Could you please more details about your machine and OS, including its version? It may be related to #95. Please, read that issue to check if is the same symptom. |
@Nikosovar I said Debian 11 VM, but you did not specify your machine, cpu, OS, OS version ... VM has a bunch of configurations related to the machine, it could be a firewall rule, if you are running in Mac, it can be the Stealth mode, ... |
Hello @uilianries . Thanks your reply. My machine is a windows 7 (i know it's maybe not helping) From now i running out of idea to make it work. I'll check on the VM configuration side (I use VirtualBox 6.0) Do you have more suggestion ? Regards, |
@Nikosovar Windows 7 is EOL since 2020. My suggestion is updating to Window 10 or 11. I'll try on Windows 10 (my machine), just in case, but I won't be able to run Windows 7 here. Also, you don't need to use VM, you can run Docker desktop directly on Windows. Please, open a separated issue to discuss your problem, because you have another configuration. |
git clone https://github.com/conan-io/training
cd training/docker_environment
docker-compose up -d
docker exec -it conan-training bash
error
xecutor failed running [/bin/sh -c /scripts/bootstrap-artifactory-config.sh]: exit code: 152
ERROR: Service 'jfrog-artifactory-training' failed to build : Build failed
LKLD-C02FN499:docker_environment chirag.shah$ view /scripts/bootstrap-artifactory-config.sh
The text was updated successfully, but these errors were encountered: