You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One thing I notice is that nothing is written in ${DOCKERDIR}/unifi-network-application/data
But I can enter the container (/BIN/BASH) and see the directory and create files etc without issues.
Environment
- OS: Ubuntu 22.04.4 LTS
- How docker service was installed:
CPU architecture
x86-64
Docker creation
I use the composer configuration as stated above.
Container logs
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 997
───────────────────────────────────────
Linuxserver.io version: 8.5.6-ls68
Build-date: 2024-10-22T17:31:57+00:00
───────────────────────────────────────
*** Waiting for MONGO_HOST unifi-db to be reachable. ***
Generating 4,096 bit RSA key pair and self-signed certificate (SHA384withRSA) with a validity of 3,650 days
for: CN=unifi
[custom-init] No custom files found, skipping...
[ls.io-init] done.
The text was updated successfully, but these errors were encountered:
Is there an existing issue for this?
Current Behavior
I recreate the container and pull the latest image. The container is recreated, and boots up. I'm presented with this screen:
Expected Behavior
I expect my settings to still be there and to just upgrade the container. I have to restore a backup everytime I upgrade to get my stuff back.
Steps To Reproduce
One thing I notice is that nothing is written in
${DOCKERDIR}/unifi-network-application/data
But I can enter the container (/BIN/BASH) and see the directory and create files etc without issues.
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: