Styles not being applied in docker environment local install. #8122
Replies: 4 comments 1 reply
-
I am moving this to a discussion as there is no confirmed bug at the moment. @vishnu-narayanan Can you please help here? |
Beta Was this translation helpful? Give feedback.
-
Are the docs at environment-setup docker updated? Because in the docker-compose file it looks like the file pulls from |
Beta Was this translation helpful? Give feedback.
-
I have the same problem |
Beta Was this translation helpful? Give feedback.
-
@arielcorte were you able to fix this? I can see that the webpack container crashes with the error - "yarn not found" and I believe that's the reason styles are not getting applied. |
Beta Was this translation helpful? Give feedback.
-
Describe the bug
I've followed the guide in docker environment setup.
First it failed because of some permission denied error, fixed by using command
docker compose build --no-cache base
or by usingmaster
branchThen when it finally worked, I go to
localhost:3000
and I see this:The app seems to work, I can login with the default dev credentials, but cant get the app to apply the styles.
I tried then running
make burn
(following project-setup) but that brings a lot of other problems such as the pg, which I couldn't fix with the common error page, or a permission error. Also I don't think it is the path to follow since I'm using docker and I shouldn't have to install something locally.The line in the
docker compose up
logs that give me a smell isI tried entering the chatwoot:development container shell, run
node -v
and it returns18.x.x
. I update nodejs-current manually from shell to version20.x.x
and nothing fixes.Maybe I'm getting something wrong cause I couldn't find any other issue with this error other than this one, which is in self hosted linux and not in docker.
To Reproduce
.env
file and the same password todocker-compose.yaml
.sudo docker compose build --no-cache base
.sudo docker compose run --rm rails bundle exec rails db:chatwoot_prepare
.sudo docker compose up
(even if the containers were running).localhost:3000
and it shows the login app all broken up.Expected behavior
To run the app via docker without any errors and show exactly the same as if it was hosted in another platform.
Environment
Docker
Cloud Provider
None
Platform
None
Operating system
Fedora 38
Browser and version
Google Chrome 117.0.5938.149
Docker (if applicable)
docker version
Client: Docker Engine - Community
Version: 24.0.6
API version: 1.43
Go version: go1.20.7
Git commit: ed223bc
Built: Mon Sep 4 12:33:40 2023
OS/Arch: linux/amd64
Context: default
docker info
Client: Docker Engine - Community
Version: 24.0.6
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.11.2
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.21.0
Path: /usr/libexec/docker/cli-plugins/docker-compose
docker compose version
Docker Compose version v2.21.0
Additional context
No response
Beta Was this translation helpful? Give feedback.
All reactions