slimtoolkit / slimtoolkit/slim
Xvfb issues after slim build
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.4k
- Forks
- 840
- PR merge metrics
- No merged PRs in 30d
Description
Greetings, i am trying to slim https://github.com/cypress-io/cypress-docker-images/tree/master/included/4.0.2
Using command (MAC): ./docker-slim build cypress/included:4.0.2 --http-probe=false
(I am also tried to use --from-dockerfile solution)
But i am getting this error on container run:
Xvfb exited with a non zero exit code.
There was a problem spawning Xvfb.
This is likely a problem with your system, permissions, or installation of Xvfb.
Error: (EE)
Fatal server error:
(EE) Could not create lock file in /tmp/.tX99-lock
Platform: linux (4.19.76-linuxkit)
Cypress Version: 4.0.2
Can you suggest how it can be fixed or debugged? 2.9GB->733mb is an impressive result, i am really interested in finding workaround here. The fat image and original image are 100% working.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the reported docker-slim command with cypress/included:4.0.2 and compare the slim image with the working fat and original images. Inspect the container's Xvfb startup and /tmp lock-file behavior; done means identifying the slimming-related cause and documenting or validating a workaround.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cypress, docker
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100