I'm trying to run this container on Zimaos, and it seems like eventually, the entire container gets reset, keeping none of its configurations, thus I need to configure the entire container again. am I misunderstanding how to use the container? it seems like my other containers run fine, but since this is a custom app, I don't really understand how or why this one is different. here is my compose yaml, maybe someone may be able to detect why I can't keep my settings permanently:
networks:
zima-bridge:
name: zima-bridge
ipam: {}
external: true
services:
explo:
command: null
container_name: explo
deploy:
resources:
limits:
memory: 4GB
cpus: "1.00"
reservations:
memory: 256MB
cpus: "0.00"
placement: {}
entrypoint: null
environment:
GUID: "0"
PUID: "0"
TZ: America/Los_Angeles
WEB_UI: "true"
image: ghcr.io/lumepart/explo:latest
networks:
- zima-bridge
ports:
- mode: ingress
target: 7288
published: "7288"
protocol: tcp
restart: unless-stopped
volumes:
- type: bind
source: /tmp/casaos-compose-app-697931657/explo/.env
target: /opt/explo/.env
bind:
create_host_path: true
- type: bind
source: /DATA/AppData/explo/opt/explo/config
target: /opt/explo/config
bind:
create_host_path: true
- type: bind
source: /DATA/Media/Music
target: /ZimaOS-HD/Media/Music
volume: {}
x-casaos:
hostname: ""
index: /7288
is_uncontrolled: false
main: explo
port_map: "7288"
scheme: http
store_app_id: compose-f26169401620f039
title:
custom: Explo
sources keep telling me that zimaos is an "immutable system" so no changes are permanent, but if that's true, why would ANYTHING work? there must be persistent ways to configure custom apps that allow them to work properly, because my other apps DO work, I'm just not familiar enough with containers and this OS to understand how to do it for custom ones
I'm trying to run this container on Zimaos, and it seems like eventually, the entire container gets reset, keeping none of its configurations, thus I need to configure the entire container again. am I misunderstanding how to use the container? it seems like my other containers run fine, but since this is a custom app, I don't really understand how or why this one is different. here is my compose yaml, maybe someone may be able to detect why I can't keep my settings permanently:
sources keep telling me that zimaos is an "immutable system" so no changes are permanent, but if that's true, why would ANYTHING work? there must be persistent ways to configure custom apps that allow them to work properly, because my other apps DO work, I'm just not familiar enough with containers and this OS to understand how to do it for custom ones