Replies: 6 comments
-
Hi @kevin-pek, can you please provide a full docker build log? My gut feeling is that pip didn't pick the right wheel file. |
Beta Was this translation helpful? Give feedback.
-
Sure! Here is the full build log:
|
Beta Was this translation helpful? Give feedback.
-
Thanks! The problem is pip downloads platform agnostic wheel for Wave (and others) as it seems like it cannot detect the platform properly:
The solution is to either specify a docker platform (should work) or find another way to tell pip which platform it should download for or take it as is and download&run waved (wave server) manually. |
Beta Was this translation helpful? Give feedback.
-
Thanks! I was also wondering if there is a page on the wave documentation that mentions that documents this? Or an example for how we can prepare a Dockerfile to download and run waved manually? |
Beta Was this translation helpful? Give feedback.
-
Unfortunately, there is not since that is outside of scope for Wave (it's about Docker/pip). |
Beta Was this translation helpful? Give feedback.
-
SOLUTION: Dockerfile
build command:
|
Beta Was this translation helpful? Give feedback.
-
Wave SDK Version, OS
Wave SDK Version: h2o-wave==1.1.1
OS: macOS (Apple Silicon, M1)
Docker Version: 24.0.2
Actual behavior
When trying to run a wave app using docker on my M1 Macbook, the container fails to start and this error is shown:
Could not connect to Wave server. Please start the Wave server (waved or waved.exe) prior to running any app.
Expected behavior
The container should start with no errors. The same dockerfile works as expected on windows, and also works on my mac when the build target platform is set to
linux/amd64
.Steps To Reproduce
To quickly reproduce this issue, you can build and run the following image based on the
wave init
hello_world example on mac.The error described should be displayed when trying to start a container.
Beta Was this translation helpful? Give feedback.
All reactions