creativecommons/cc-resource-archive

[Bug] Inconsistent docker behavior - parsing Gemfile

Murdock9803 opened this issue · 3 comments

Murdock9803 commented

Description

While trying to preview the site from our local clone, the command docker compose up results in an error message while parsing the Gemfile in the last step of the Dockerfile commands, that is RUN bundle install .
The message says : `failed to solve: process "/bin/sh -c bundle install" did not complete successfully: exit code:4

Reproduction

  1. Clone the repository in your local machine (main branch)
  2. Change the directory to your clone in the terminal
  3. In the terminal, enter the command docker compose up
  4. See error.

Expectation

The docker image should build as earlier it used to, by the command docker compose up and users should be able to have a preview of the site in their local machine storage.

Screenshots

error image

Environment

  • Device: Laptop - HP Pavillion Gaming 15
  • OS: Microsoft Windows 11 - version 10.0.22631
  • Docker version: 25.3
  • docker-compose version: v2.24.5
  • wsl version:
    Screenshot 2024-06-12 003223

Resolution

  • I would be interested in resolving this bug.
Murdock9803 commented

@possumbilities I would like to inform that the issue is created.

possumbilities commented

I was able to relatedly reproduce this on a linux dev container with VS Code Ubuntu 20.04.6 LTS

Screen Shot 2024-06-10 at 10 24 56 AM

The error differs from the screenshot on Windows, but I suspect that the Linux error might be more accurate in determining a cause.

After walking back through recent changes to Docker it appears that the introduction of the prettier node container introduced a breaking change to the Docker environment; it is likely this has more to do with the configuration changes in the files or the locations of files rather than the node container itself:

I removed these changes with a testing branch revert-docker, and the Docker environment runs correctly again. Ayush also tested it on Windows and it works again there as well:

Digging deeper into what the cause is here I found these:

  • 👍1
possumbilities commented

As this is a breaking change, blocking current work my current plan at the moment is to clean up the revert-docker branch, and initiate a PR for it. We can then continue investigating what caused this Issue with the new Docker configuration with the addition of the node container, correct that and then add it back in.

If that's what happens I'll return here with an update.

  • ❤️1