invalid character 's' looking for beginning of value #6575

Yalchin403 · 2022-11-14T12:35:00Z

[ x] I have tried with the latest version of Docker Desktop
[ x] I have tried disabling enabled experimental features
I have uploaded Diagnostics
Diagnostics ID: 37BCADF4-8FCF-4E92-B2F6-C0DDA2AFA113/20221115000422

Expected behavior

I would normally expect my containers and docker to be running without a problem.

Actual behavior

It usually doesnt happen with my other project set up, it only happens with one of my projects. But this problem doesnt happen in my windows with the exactly same setup. Once I start containers, after some time docker icon starts to play, and it stops. not just tops but it gets unable to restart or quit. I need to restart the laptop get it back. I tried reinstall, factory reset, deleting all images and containers, and making them again. But problem persists.

Information

macOS Version:
Intel chip or Apple chip:
Apple chip m2
Docker Desktop Version:
4.14.0

Output of `/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check`

Steps to reproduce the behavior

...
...

The text was updated successfully, but these errors were encountered:

Yalchin403 · 2022-11-17T11:28:50Z

The issue doesn't happen with the version 4.12.0

stuartherbert · 2022-11-23T09:06:10Z

I've been plagued with this exact same issue too.

Can confirm that it never happened with 4.12.0.
I'm on Apple M1 not M2.
Happens for projects running x86 containers.
Happens for projects running only arm64 containers.
I can restart Docker by first going into Application Monitor and force-quitting all of the docker processes.

I have a second machine that has never run x86 containers. To date, it has never had this problem. May or may not be relevant.

This bug is incredibly disruptive.

sjuanati · 2022-11-23T11:02:07Z

Same problem here with chipset Apple M1 Max.
After docker (4.14.1) is running for a few minutes, I get the error:

`invalid character 's' looking for beginning of value`

and then I have to kill all processes and restart docker.

sebmasterid · 2022-12-13T14:13:21Z

Same problem with Intel Mac Book with or without Virtualiation framework, with gRPC Fuse or VirtioFS.
Docker desktop version 4.15.0

crisanmm · 2022-12-13T16:29:19Z

Same error on M1 Max, macOS 13.0.1, Docker Desktop 4.15.0

I downgraded Docker Desktop to 4.12.0 and it's working fine so far. The steps I followed for downgrading are here https://stackoverflow.com/questions/62217678/can-i-roll-back-to-a-previous-version-of-docker-desktop/64825028#64825028

acbramley · 2022-12-22T22:14:24Z

I was getting the same issue running selenium tests (using selenium/standalone-chrome:4.5.2-20221021) on one of my projects, downgrading to 4.12.0 also fixed it for me

Before this change, you would see an error message like: ``` error waiting for container: invalid character 's' looking for beginning of value ``` here's an example: docker/for-mac#6575 (comment) After this change, you get an error message like: ``` error waiting for container: copying response body from Docker: unexpected EOF ``` which is a bit more explieict. Signed-off-by: Nick Santos <nick.santos@docker.com>

Before this change, you would see an error message like: ``` error waiting for container: invalid character 's' looking for beginning of value ``` here's an example: docker/for-mac#6575 (comment) After this change, you get an error message like: ``` error waiting for container: copying response body from Docker: unexpected EOF ``` which is a bit more explicit. Signed-off-by: Nick Santos <nick.santos@docker.com>

richardtape · 2022-12-30T00:18:56Z

This is still an issue with version 4.15.0 (93002), M1, Mac OS 13.1.0.

I have no idea if it's related, but running /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check after I have restarted Docker after a crash like above, I get one failed test with the error

[FAIL] DD0019: is the com.docker.vmnetd process responding? failed to ping vmnetd with error: failed to connect to /var/run/com.docker.vmnetd.sock: is vmnetd running?: dial unix /var/run/com.docker.vmnetd.sock: connect: no such file or directory

Repro steps: - Run Docker Desktop - Run `docker run busybox tail -f /dev/null` - Run `pkill "Docker Desktop" Expected: An error message that indicates that Docker Desktop is shutting down. Actual: An error message that looks like this: ``` error waiting for container: invalid character 's' looking for beginning of value ``` here's an example: docker/for-mac#6575 (comment) After this change, you get an error message like: ``` error waiting for container: copying response body from Docker: unexpected EOF ``` which is a bit more explicit. Signed-off-by: Nick Santos <nick.santos@docker.com>

HendrikLevering · 2023-01-04T06:17:26Z

I get the same error with 4.15.0, M1, Mac OS 13.1.0
After the error happens nothing works to restart docker. I have to restart my laptop to get docker running again.

willbenica · 2023-01-20T09:33:26Z

Just ran into this again. It's been plaguing me for a few months now.
docker v4.15.0 and running macos v12.6.2

philimat · 2023-01-20T15:56:30Z

I believe this thread may be suffering from the same issue as being discussed in #6530. There was a fix rolled into version 4.16, so I would encourage those of you in this thread to upgrade to that version and see if solves the issue.

xkszltl · 2023-01-22T18:50:31Z

We're seeing this very frequently on macOS 12 (x86) + 4.16.2 (95914), even with a simple interactive docker run of bash, sometimes it quit after a while of idling, with:

ERRO[0585] error waiting for container: invalid character 'c' looking for beginning of value

The taskbar icon of docker desktop will show the booting animation, seems something's restarting, but taking forever.
After killing the docker desktop process, the next start will fail with that troubleshooting dialog, and factory reset won't help.

OS reboot, or killing com.docker.backend, will help restore everything back to normal.

I also found this old issue may be related, although not many answers there either:

erro[0149] error waiting for container: invalid character 'u' looking for beginning of value #5139

willbenica · 2023-01-23T07:18:40Z

I believe this thread may be suffering from the same issue as being discussed in #6530. There was a fix rolled into version 4.16, so I would encourage those of you in this thread to upgrade to that version and see if solves the issue.

After seeing this, I updated docker and started the containers that I normally start. I left docker running over the weekend and didn't really do anything.

Came back to it this morning, and I have the same error as in the description. It doesn't seem that 4.16 fixes the issue.

jrusev · 2023-01-25T20:27:07Z

I am getting invalid character 's' looking for beginning of value after running a cadence server container for a while (couple of minutes). Happens every time. I have to stop docker by killing the docker backend process, and restarting Docker Desktop. I was running the same container before without issues (last year).

I am running Docker Desktop 4.15.0, on macOS Ventura, MacBook Pro 2019.

Repro steps: - Run Docker Desktop - Run `docker run busybox tail -f /dev/null` - Run `pkill "Docker Desktop" Expected: An error message that indicates that Docker Desktop is shutting down. Actual: An error message that looks like this: ``` error waiting for container: invalid character 's' looking for beginning of value ``` here's an example: docker/for-mac#6575 (comment) After this change, you get an error message like: ``` error waiting for container: copying response body from Docker: unexpected EOF ``` which is a bit more explicit. Signed-off-by: Nick Santos <nick.santos@docker.com>

Repro steps: - Run Docker Desktop - Run `docker run busybox tail -f /dev/null` - Run `pkill "Docker Desktop" Expected: An error message that indicates that Docker Desktop is shutting down. Actual: An error message that looks like this: ``` error waiting for container: invalid character 's' looking for beginning of value ``` here's an example: docker/for-mac#6575 (comment) After this change, you get an error message like: ``` error waiting for container: copying response body from Docker: unexpected EOF ``` which is a bit more explicit. Signed-off-by: Nick Santos <nick.santos@docker.com> (cherry picked from commit 9900c7a) Signed-off-by: Sebastiaan van Stijn <github@gone.nl>

Repro steps: - Run Docker Desktop - Run `docker run busybox tail -f /dev/null` - Run `pkill "Docker Desktop" Expected: An error message that indicates that Docker Desktop is shutting down. Actual: An error message that looks like this: ``` error waiting for container: invalid character 's' looking for beginning of value ``` here's an example: docker/for-mac#6575 (comment) After this change, you get an error message like: ``` error waiting for container: copying response body from Docker: unexpected EOF ``` which is a bit more explicit. Signed-off-by: Nick Santos <nick.santos@docker.com>

eduardocque · 2023-02-19T08:47:34Z

+1

falbuixech · 2023-02-20T08:17:51Z

This happens to me on Windows, so it doesn't seem like a Mac only problem. More details on:

AbdBarho/stable-diffusion-webui-docker#336

Edit: Solved updating my pip version.

carlostrujillosamper · 2023-02-28T16:09:42Z

I deselected that and it seemed to fix the issue. I tried everything talked about on this thread and this is what ultimately fixed it. I'm on mac M1 , docker desktop version 4.16.2 (95914)
Hope this helps

cybertunnel · 2023-03-13T19:35:19Z

I can confirm turning off the Docker Compose V2 fixes the invalid character '[char]' looking for beginning of value error where [char] is any character. In this issue it is s.
I am running on macOS on latest version of docker and macOS with this issue. Hoping it is just a bug and a simple fix for the devs. Appreciate all the work everyone on this project does! 🥂

RyadMM · 2023-03-20T13:10:54Z

I am having the same issue and I tried everything mentioned, still get the error. Driving me crazy. Did multiple re-install, uncheck docker compose V2, clean purge data, factory resets, updating pip version, uncheck experimental features etc. still getting the error.

Every time I have to kill all docker activity from the activity monitor.

I am running on mac m1, latest docker version v4.17.0, big sur

samuelguesnier · 2023-04-03T00:16:26Z

On Windows, I went to C:\Users\sam\AppData\Roaming\Docker , opened locked-directories file and replaced content with {} , then save file and restart docker desktop

adamantal · 2023-04-19T13:57:33Z

Unchecking compose V2, reinstalling Docker, clearing Docker cache, disabling experimental features did not resolve the problem for me.

Downgrading to 4.12.0 solves the issue, but is not a long-term solution

SammySkycrafts · 2023-04-19T14:15:29Z

This issue is affecting me and another user too - Last known working version is 4.12.0 but as stated above, running this is not a long term solution and i am finding myself wanting to update however cannot due to the fact it will break some containers.

I did read in another issue that it is to do with sending large volumes of data via UDP - I can confirm that in the minutes before the error the container has significant netowrking issues (failres in name resolution, failures to connect).

ColeDCrawford · 2023-04-24T15:21:37Z

Also experiencing this. Very disruptive.

MashinaMashina · 2023-04-24T16:34:33Z

I am getting this error on version 4.16.3

docker stops itself a few minutes after starting

sequencing:

$ docker-compose up
... working...
invalid character 's' looking for beginning of value
$ docker-compose up
docker: Error response from daemon: open \\.\pipe\docker_engine_linux: The system cannot find the file specified.

biggeR-data · 2023-06-05T17:07:36Z

Updating to version 4.20.1 resolved the error invalid character 's' looking for beginning of value on Windows 11 / WSL2 Ubuntu (added this since other comments were also related to Windows).

wimleers · 2023-08-14T16:26:55Z

Just ran into this for the very first time, Docker Desktop 4.7.1, which has been otherwise running fine for many months.

Docker pretends the container is still running when it is not. 😮

nicks · 2023-08-14T16:56:17Z

Hi all! Thanks for reporting these issues.

As far as I can tell, there are a few different bugs being reported here, and many (all?) of them have been fixed in newer versions of Docker Desktop (e.g., the selenium problem reported in this comment #6575 (comment) which is tracked here: #6530)

The exact error message "invalid character 's' looking for beginning of value" is a bit of a red herring. It means that something in the engine failed, but doesn't give you any useful information into what failed.

The message is due to a bug in the Docker CLI error-handling that is fixed here: moby/moby#44739. We don't expect this error message to show up anymore in new versions of Docker Desktop.

If you still see issues after upgrading to Docker Desktop 4.22, please open a new issue, so we can track it separately. Thanks!

CoderMiguel · 2023-10-06T13:20:59Z

I am running several versions of Docker from 4.18 to 4.22 and still getting this error.

Will update to the latest versions but I suspect this issue is still lurking past the changes assumed to have resolved this issue.

docker-robott added the version/4.14.0 label Nov 15, 2022

nicks mentioned this issue Jan 3, 2023

client: improve error messaging on crash moby/moby#44739

Merged

thaJeztah mentioned this issue Jan 30, 2023

[23.0 backport] client: improve error messaging on crash moby/moby#44883

Merged

This was referenced Feb 4, 2023

vendor: github.com/docker/docker v23.0.0 docker/cli#4002

Merged

[23.0 backports] assorted backports docker/cli#4004

Merged

AbdBarho mentioned this issue Feb 19, 2023

Invalid character 's' AbdBarho/stable-diffusion-webui-docker#336

Closed

2 tasks

nicks closed this as completed Aug 14, 2023

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

invalid character 's' looking for beginning of value #6575

invalid character 's' looking for beginning of value #6575

Yalchin403 commented Nov 14, 2022 •

edited

Yalchin403 commented Nov 17, 2022

stuartherbert commented Nov 23, 2022

sjuanati commented Nov 23, 2022 •

edited

sebmasterid commented Dec 13, 2022

crisanmm commented Dec 13, 2022

acbramley commented Dec 22, 2022 •

edited

richardtape commented Dec 30, 2022

HendrikLevering commented Jan 4, 2023

willbenica commented Jan 20, 2023

philimat commented Jan 20, 2023

xkszltl commented Jan 22, 2023

willbenica commented Jan 23, 2023

jrusev commented Jan 25, 2023 •

edited

eduardocque commented Feb 19, 2023

falbuixech commented Feb 20, 2023 •

edited

carlostrujillosamper commented Feb 28, 2023

cybertunnel commented Mar 13, 2023

RyadMM commented Mar 20, 2023 •

edited

samuelguesnier commented Apr 3, 2023

adamantal commented Apr 19, 2023

SammySkycrafts commented Apr 19, 2023 •

edited

ColeDCrawford commented Apr 24, 2023

MashinaMashina commented Apr 24, 2023

biggeR-data commented Jun 5, 2023 •

edited

wimleers commented Aug 14, 2023

nicks commented Aug 14, 2023

CoderMiguel commented Oct 6, 2023 •

edited

invalid character 's' looking for beginning of value #6575

invalid character 's' looking for beginning of value #6575

Comments

Yalchin403 commented Nov 14, 2022 • edited

Expected behavior

Actual behavior

Information

Output of /Applications/Docker.app/Contents/MacOS/com.docker.diagnose check

Steps to reproduce the behavior

Yalchin403 commented Nov 17, 2022

stuartherbert commented Nov 23, 2022

sjuanati commented Nov 23, 2022 • edited

sebmasterid commented Dec 13, 2022

crisanmm commented Dec 13, 2022

acbramley commented Dec 22, 2022 • edited

richardtape commented Dec 30, 2022

HendrikLevering commented Jan 4, 2023

willbenica commented Jan 20, 2023

philimat commented Jan 20, 2023

xkszltl commented Jan 22, 2023

willbenica commented Jan 23, 2023

jrusev commented Jan 25, 2023 • edited

eduardocque commented Feb 19, 2023

falbuixech commented Feb 20, 2023 • edited

carlostrujillosamper commented Feb 28, 2023

cybertunnel commented Mar 13, 2023

RyadMM commented Mar 20, 2023 • edited

samuelguesnier commented Apr 3, 2023

adamantal commented Apr 19, 2023

SammySkycrafts commented Apr 19, 2023 • edited

ColeDCrawford commented Apr 24, 2023

MashinaMashina commented Apr 24, 2023

biggeR-data commented Jun 5, 2023 • edited

wimleers commented Aug 14, 2023

nicks commented Aug 14, 2023

CoderMiguel commented Oct 6, 2023 • edited

Yalchin403 commented Nov 14, 2022 •

edited

Output of `/Applications/Docker.app/Contents/MacOS/com.docker.diagnose check`

sjuanati commented Nov 23, 2022 •

edited

acbramley commented Dec 22, 2022 •

edited

jrusev commented Jan 25, 2023 •

edited

falbuixech commented Feb 20, 2023 •

edited

RyadMM commented Mar 20, 2023 •

edited

SammySkycrafts commented Apr 19, 2023 •

edited

biggeR-data commented Jun 5, 2023 •

edited

CoderMiguel commented Oct 6, 2023 •

edited