adjusting README and Dockerfile for x86_64 and arm64 usage

[Urfoex]

No description provided.

[Urfoex]

Solves #19

[alxn4]

Thanks for your updates! Can we add a more meaningful error message when we try to spin up the image on macos or windows host system? Right now I am receiving the following message:

 ~/code17/getml-demo  update_readme_1_4_0 ?1  docker-compose up notebooks --build                                          17 err  23:37:21
[+] Building 0.0s (1/1) FINISHED                                                                                        docker:desktop-linux
 => [notebooks internal] load build definition from Dockerfile                                                                          0.0s
 => => transferring dockerfile: 959B                                                                                                    0.0s
failed to solve: failed to parse platform : "" is an invalid component of "": platform specifier component must match "^[A-Za-z0-9_-]+$": invalid argument

On a minor note, please use the <randomly_generated_token> placeholder consistently.

[srnnkls]

This should just run on macOS and there should be no error at all. Will have a look in a few minutes.

The error indicates that the build arg is not populated on macOS.

[srnnkls]

The problem here is the redefinition of the TARGETPLATFORM arg in line 1 of the Dockerfile. Just remove it and everything should work as expected.

The use of build args in docker is a little tricky:
If you use the ARG directive outside of build stages you are declaring the arg, if you use it inside a build stage, you are making the arg defined outside visible to the stage. In this case the arg was prepopulated, so no need to declare it. And as you are reference it only from the outside (in the FROM directive) you don't need to make it visible to the build stage at all.

[srnnkls]

But was it actually working with podman, @Urfoex?

[srnnkls]

On a minor note, please use the <randomly_generated_token> placeholder consistently.

I would add that the users shouldn't be concerned about the stochastic nature of the token at all: Just name it <token>.

[srnnkls]

Some small comments. Otherwise LGTM. Great work!

[Urfoex]

But was it actually working with podman, @Urfoex?

Yeah, I guess podman sees "These arguments are defined in the global scope" differently then docker.
But the TARGETPLATFORM is not needed here anyway, as "By default, the target platform of the build request is used."
So I threw it out.

On a minor note, please use the <randomly_generated_token> placeholder consistently.

Adjusted.

I would add that the users shouldn't be concerned about the stochastic nature of the token at all: Just name it .

I put <generated_token> to distinguish it from token in the monitor part, as that is set by hand. And <token> and token just look too similar and might confuse.

[srnnkls]

lgtm. have a good merge!