[Docker] The story that an error occurred in docker-compose up

docker-compose upWhen I did, I got the following error.

web_1     | => Booting Puma
web_1     | => Rails 6.0.3.1 application starting in development 
web_1     | => Run `rails server --help` for more startup options
web_1     | Usage: yarn [options]
web_1     | 
web_1     | yarn: error: no such option: --integrity
web_1     | 
web_1     | 
web_1     | ========================================
web_1     |   Your Yarn packages are out of date!
web_1     |   Please run `yarn install --check-files` to update.
web_1     | ========================================
web_1     | 
web_1     | 
web_1     | To disable this check, please change `check_yarn_integrity`
web_1     | to `false` in your webpacker config file (config/webpacker.yml).
web_1     | 
web_1     | 
web_1     | 
web_1     | 
web_1     | 
web_1     | Exiting
shitsumonwa_web_1 exited with code 1

No change from the above screen. .. .. Please run yarn install --check-files to update. Because there is

yarn install --check-files

And then try `` `docker-compose up``` again, the same error will be displayed.

web_1     | To disable this check, please change `check_yarn_integrity`
web_1     | to `false` in your webpacker config file (config/webpacker.yml).

Since there was the above description, I changed the contents of config / webpacker.yml.

config/webpacker.yml


development:
  <<: *default
  compile: true

  # Verifies that correct packages and versions are installed by inspecting package.json, yarn.lock, and node_modules
  check_yarn_integrity: true

It was above, but I changed it.

config/webpacker.yml


development:
  <<: *default
  compile: true

  # Verifies that correct packages and versions are installed by inspecting package.json, yarn.lock, and node_modules

#Change the following from true to false
  check_yarn_integrity: false

It worked! !! !!

web_1     | => Booting Puma
web_1     | => Rails 6.0.3.1 application starting in development 
web_1     | => Run `rails server --help` for more startup options
web_1     | Puma starting in single mode...
web_1     | * Version 4.3.5 (ruby 2.6.3-p62), codename: Mysterious Traveller
web_1     | * Min threads: 5, max threads: 5
web_1     | * Environment: development
web_1     | * Listening on tcp://0.0.0.0:3000
web_1     | Use Ctrl-C to stop

See article below

Docker-compose up is not possible due to yarn (Your Yarn packages are out of date!)

Recommended Posts

[Docker] The story that an error occurred in docker-compose up
[Docker] The story that an error occurred in docker-compose up
Eclipse error
A story that got stuck with an error during migration in docker PHP laravel
In WSL2, when I did `docker-compose up`, I got an error saying that the sh file was not found.
The story when the container does not start up with docker-compose up and an error occurs
Java Error Handling Basics-The story that catch is only picked up in the foreground
The story that led to solving the error because postgres did not start with docker-compose up
The story that Tomcat suffered from a timeout error in Eclipse
Resolved the error that occurred when trying to use Spark in an environment where Java 8 and Java 11 coexist.
The story that docker had a hard time
Docker in LXD
[AWS? Docker?] Summarize the necessary knowledge in your portfolio in an easy-to-understand manner [terraform? CircleCI?]
[Docker] The story that an error occurred in docker-compose up
Install yarn in docker image
npm error in docker tutorial
Let's summarize the Java 8 grammar from the perspective of an iOS engineer
The story of an Illegal State Exception in Jetty.
Verification value error that occurred in a clustering environment
The story that .java is also built in Unity 2018
Error in docker rails db: migrate (StandardError: An error has occurred, all later migrations canceled :)
[Docker] List of errors that occurred when building the environment
About the error that occurred when adding the column name in rails (rails db: migrate, rails db: rollback, add)
Install docker and docker-compose on ubuntu in the shortest process
npm error in docker tutorial
Autoprefixer does n’t support Node v4.8.2. Update it. Error that occurred in Rails [Docker Rails5 Bootstrap]
A story that I realized that I had to study as an engineer in the first place
The story of setting up an Oracle V $ -like thing from 0 on PostgreSQL: 12 of the official Docker image
The repository ... is not signed error in docker build apt-get update
I don't see an error in Rails bundle install ... the solution
The story that the build error did not stop when using Eclipse 2020
Explain DI in an obese story
Hit the Docker API in Rust
A story that addresses the problem that REMOTE_ADDR cannot be acquired in a cluster built with Docker Swarm + Traefik (1.7).
An error occurred in the free course of RubyOnRails Udemy, solved it, and went through to the end
[Rails] About the error that the image is not displayed in the production environment
Launching the production environment with docker + rails (ver5.2) and errors that occurred
I want to display an error message when registering in the database
The story that the Servlet could not be loaded in the Java Web application
A story about an arithmetic overflow that you shouldn't encounter in Ruby
An error occurred when executing a function from MyBatis with the OUT parameter set to CURSOR in PostgreSQL.
When introducing JOOQ to Spring boot, a story that was dealt with because an error occurred around Liquibase
The story of updating SonarQube's Docker Container
Rails refactoring story learned in the field
The story of AppClip support in Anyca
[Swift] Elements that make up the protocol
The story of writing Java in Emacs
Solution that gives an error when trying to connect to DB (MySQL) in Java
The story of making an Android application that can adjust the sampling frequency of the accelerometer
A story that an inexperienced beginner was having trouble setting up Rails Server.
When I think about the 402 error that suddenly appeared in the middle of the introduction of PAY.jp, there was an unexpected place
How to deal with the error yaml.scanner.ScannerError: while scanning for the next token that appeared in Rails environment construction with Docker