Dockerfile fails about prk_firmware HOT 7 CLOSED

right x86
doker.txt
rakenativeonmacoos.txt
thx

from prk_firmware.

@pbrena Do you use an M1 Mac? I'm not sure but M1 Mac possibly doesn't work due to the Arm architecture

(suggestion add some pointers for the environment and requisites).

OK.

from prk_firmware.

Ah, Catalina couldn't run on M1. So I totally don't know what happened on your end. Would you provide the full output message?

from prk_firmware.

@pbrena
As far as we've tested, it could build successfully. The image below is the result on macOS Catalina:

Are you sure to follow this instruction?
https://github.com/picoruby/prk_firmware/blob/master/Dockerfile#L1-L11

from prk_firmware.

i cleaned up and ran
docker build . -t prk
but i still get

=> ERROR [6/6] RUN rake setup 0.7s

[6/6] RUN rake setup:
#11 0.604 rake aborted!
#11 0.604 No Rakefile found (looking for: rakefile, Rakefile, rakefile.rb, Rakefile.rb)
#11 0.604
#11 0.604 (See full trace by running task with --trace)

so i cant Setup... i dont know what to do

from prk_firmware.

The message changed. It says you simply don't have Rakefile in the top directory.
I would think you have to learn programming basics, to be exact, how to use Linux/Unix command line and how to read an error message.
Really sorry but I am closing this issue because I believe the problem isn't on our end

from prk_firmware.

I understand and dont complain, Im a newbie and will keep on reading, and further learning.

Having said that, I just want to point out something...

As far as I understand the guide... the setup command (docker build . -t prk) is the very first to be run and the user has in principle no control of what is or isnt downloaded (particularly Rakefile in the top directory) without modifying the dokerfile itself and as the container isnt created and no further command is posible... this should run as is, right?

I lost what my original deviation was so my approach was to cleanup my previos environment (following some online guides) to reinstall/upgrade Docker, (hence the change of message) and even re run the setup with --no-cache parameter to no avail...

I cannt identify the step in the dockerfile where top directory is populated but i will try to create an environment that gives a command prompt and proceed manually

from prk_firmware.