v0.4.1: x86_64 getting stuck with qemu64 cpu #288
Comments
sadbuttrue1
changed the title
|
Can you kindly try again with |
|
If I delete it with and everything docker related will be stuck. |
Yes, I can try it with I didn't try it with |
|
Result of With |
|
Does specifying |
|
@sadbuttrue1 I have been able to reproduce it, using I need to figure out why the default config stops working. |
|
@abiosoft, with |
abiosoft
changed the title
|
As a side note, is x86_64 emulation your primary use-case? I would expect the degraded performance to discourage extensive use. |
|
Yes, I'm using it to run https://hub.docker.com/_/microsoft-mssql-server. |
Not at all, it will be similar performance to the default processor. I'm only referring to the fact that emulation is always noticeably slower than native architecture. |
|
@sadbuttrue1 Do put your "me too" on microsoft/mssql-docker#734 - when they get to that it will make a big difference. |
|
same issue here...
For my use case: x86 emulation is usually used to test some images that do not provide arm support; or in some cases we need to build x86 docker image to push to a remote server to run it. |
|
@mritd specifying Looking at lima-vm/lima#641 I can see the previous default value was |
|
Oh sorry, I forgot to mention... I tested |
@mritd you mean it's slower than before? |
|
@abiosoft Just feeling, I didn't do the full test. |
|
My environment I got the same error after start and pull some docker image. But it working fine with Below is information about the QEMU process. And serial.log of colima |
|
I have just upgraded too and while the start command worked the 2nd time, any docker command or even Is there a start command that still works, even if slower? (I have M1 Max anyway) |
|
This is most of the Dockerfile that seems to break it. It's essentially SQL Server with enabled Free Text Search. It worked just fine with older version of colima, and it has not been modified recently # Using non default image as Full-text search support is not included in it
# This image implements https://schwabencode.com/blog/2019/10/27/MSSQL-Server-2017-Docker-Full-Text-Search
# We can implement it ourselves,
# but our Dockerfile is rebuilt with the local script and the steps in the image very slow.
# It's a specific tag, verifiable at https://hub.docker.com/r/benjaminabt/mssql-fts/tags
FROM benjaminabt/mssql-fts:2019-cu10-ubuntu-2004
ENV ACCEPT_EULA Y
# ENV MSSQL_PID # Does not matter
ENV MSSQL_SA_PASSWORD DoesNotMatter
# Missing from the base image: `mssql-tools`, needs above ACCEPT_EULA env variable set first
# Found via https://docs.microsoft.com/en-us/sql/linux/sql-server-linux-setup-tools?view=sql-server-ver15#ubuntu
# The original image does some cleanup, so we have to repeat parts of their script. It's still faster.
RUN export DEBIAN_FRONTEND=noninteractive && \
apt-get update && \
apt-get install -yq curl apt-transport-https && \
curl https://packages.microsoft.com/keys/microsoft.asc | apt-key add - && \
curl https://packages.microsoft.com/config/ubuntu/20.04/prod.list | tee /etc/apt/sources.list.d/msprod.list && \
apt-get update && \
apt-get install -y mssql-tools unixodbc-dev && \
apt-get clean && \
rm -rf /var/lib/apt/lists
# Run SQL Server process
CMD /opt/mssql/bin/sqlservr
# ... File clipped intentionallyOnce I try to run this (via docker-compose), it hangs:
And from then on any command interacting with colima or docker hangs, even |
|
@Meligy I think you should try with below two ways:
Or See
After this issue is fixed, we can use Colima agian 😄 |
|
Can you all try the development version with If it works fine, a new release will be made. |
|
@abiosoft thanks a lot. It seems quite slow though. For the above image with this command (without explicitly setting colima start --arch x86_64 --cpu 4 --memory 4 --disk 60The extraction time is quite too slow (I don't have a baseline to compare to, but it feels way way slower). Same for running the apt commands in the Dockerfile, and for starting SQL Server and running a handful SQL scripts.
However, this is still an improvement over not working at all though. |
|
@Meligy thanks for the feedback, I would investigate a bit more. |
|
I also tried the last "released" version (not colima start --arch x86_64 --cpu 4 --memory 4 --disk 60 --cpu-type Haswell-v4I set The non-scientific results were pretty comparable times, if not tiny bit slower maybe.
I think this makes |
|
can anyone confirm if the latest development version |
|
@abiosoft thanks heaps for this. It's much better. I deleted the old one, installed the colima start --arch x86_64 --cpu 4 --memory 4 --disk 60And then my timings were at least 50% less. You can compare this pic with above screenshots:
The actual container performance, seems much improved as well, as you see waiting for SQL Server to start and running a. handful small scripts now takes half a minute (last number) instead of 3.5+ minutes. Thanks again. |
|
@Meligy will push out a new release shortly. Thanks for confirming. |
|
Fix now in stable version https://github.com/abiosoft/colima/releases/tag/v0.4.2 |
|
Thanks heaps. |
Updated colima from 0.3.4 to 0.4.1.
Did
colima deleteandcolima start(colima start --arch amd --cpu 4 --memory 4to be precise).Got
Here is log after starting:
serial.log
macOS version 12.3.1
CPU Apple M1 Max
colima version 0.4.1
lima version 0.10.0
qemu version 6.2.0_1
The text was updated successfully, but these errors were encountered: