Open flavorgold1 opened 1 year ago
this would be fixed if https://github.com/pawelmalak/flame/pull/356 was ever merged
A "pure docker-compose" workaround is to use the following docker-compose file:
services:
flame_guest:
container_name: flame_guest
image: pawelmalak/flame:latest
user: 1000:1000
network_mode: host
volumes:
- /path/to/data:/app/data
- ./initialFiles.empty.json:/app/utils/init/initialFiles.json:ro
- ./path/to/data/flame.css:/app/public/flame.css:ro
- /var/run/docker.sock:/var/run/docker.sock
environment:
- TZ=Etc/GMT
- PASSWORD=password_here
restart: unless-stopped
command: "node server.js"
You also need to create the following file where the docker-compose file is located (named initialFiles.empty.json
):
{
"files": []
}
This will be used here: https://github.com/pawelmalak/flame/blob/446b4095f6bb06e0f878efb4ac1f990a5ae7d39c/utils/init/initFiles.js#L5
You also need to override the CMD from the dockerfile (hence the command: "node server.js"
at the end of the docker-compose)
@GitKepler Does this still workaround still work?
What should flame.css contain? (and should it be read-only as you specified?)
@GitKepler Does this still workaround still work?
What should flame.css contain? (and should it be read-only as you specified?)
./path/to/data/flame.css
contains your custom CSS code (the one you set in Flame UI).
You can leave it empty (in which case the only customization that will be applied is from the theme you choose).
As for read-only, in my case I do not need to modify it, however if you intend to modify the CSS later on using the web UI, removing the read-only flag would make sense.
The workaround still works with the latest version.
My
docker-compose.yml
file:sudo docker logs flame_guest
:When I run
ps aux
, I can see thatnode server.js
is running asroot
instead of1000:1000
as it should be.