birdistelive docker container not staying up
slfhstr opened this issue · comments
Installed as per instructions
docker ps -a shows container restarting when website page reloaded (or more frequently)
website page shows error 500
Would love to get this running if possible
Sorry you have issues with it.
Can you look at the logs? Just use docker logs <id container>.
On what kind of hardware are you using the app?
EnvironmentName Production
warn: Microsoft.AspNetCore.DataProtection.Repositories.FileSystemXmlRepository[60]
Storing keys in a directory '/root/.aspnet/DataProtection-Keys' that may not be persisted outside of the container. Protected data will be unavailable when container is destroyed.
info: Microsoft.Hosting.Lifetime[0]
Now listening on: http://[::]:80
info: Microsoft.Hosting.Lifetime[0]
Application started. Press Ctrl+C to shut down.
info: Microsoft.Hosting.Lifetime[0]
Hosting environment: Production
info: Microsoft.Hosting.Lifetime[0]
Content root path: /app
info: Microsoft.Hosting.Lifetime[0]
Application is shutting down...
Using VPS with Ubuntu 20.04
Weird.
Can you post me your cpu details via lscpu?
Also, can you provide me your docker-compose file? (please change the twitter api key and other sensitive info like the db password before providing it).
lscpu :
Architecture: x86_64
CPU op-mode(s): 32-bit, 64-bit
Byte Order: Little Endian
Address sizes: 46 bits physical, 48 bits virtual
CPU(s): 8
On-line CPU(s) list: 0-7
Thread(s) per core: 1
Core(s) per socket: 1
Socket(s): 8
NUMA node(s): 1
Vendor ID: GenuineIntel
CPU family: 6
Model: 79
Model name: Intel(R) Xeon(R) CPU E5-2650 v4 @ 2.20GHz
Stepping: 1
CPU MHz: 2199.996
BogoMIPS: 4399.99
Hypervisor vendor: KVM
Virtualization type: full
L1d cache: 256 KiB
L1i cache: 256 KiB
L2 cache: 32 MiB
L3 cache: 128 MiB
NUMA node0 CPU(s): 0-7
Vulnerability Itlb multihit: Not affected
Vulnerability L1tf: Mitigation; PTE Inversion
Vulnerability Mds: Mitigation; Clear CPU buffers; SMT Host state unknown
Vulnerability Meltdown: Mitigation; PTI
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1: Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2: Mitigation; Full generic retpoline, IBPB conditional, IBRS_FW, STIBP disabled, RSB filling
Vulnerability Srbds: Not affected
Vulnerability Tsx async abort: Mitigation; Clear CPU buffers; SMT Host state unknown
Flags: fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ss syscall nx
pdpe1gb rdtscp lm constant_tsc arch_perfmon rep_good nopl xtopology cpuid tsc_known_freq pni pclmulqdq ssse3 fma
cx16 pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand hypervisor lahf_lm abm
3dnowprefetch cpuid_fault invpcid_single pti ssbd ibrs ibpb stibp fsgsbase tsc_adjust bmi1 hle avx2 smep bmi2 e
rms invpcid rtm rdseed adx smap xsaveopt arat umip md_clear arch_capabilities
docker-compose.yml is the stock one from repo
Did you provide you own Twitter API key?
You can't use the stock docker-compose.yml without changing some entries (documented in the installation procedure).
Sorry, I was running out the door this morning, and that last message was not clear.
What I meant was stock docker-compose.yml with my Twitter credentials.
Do you monitor the RAM usage when the app is crashing? I've already saw dockers images crashing when they where limited on this side. BSL doesn't need much, but a least 500MB/1GB is required for the app and the database.
Sorry, I didn't, but good tip, I will try to check.
Thank you for investigating.
Hi, do you still have issues with your BSL container?