Open derMart opened 1 year ago
Seems like I'm experiencing something similar in #49 After more testing, it sometimes starts correctly, did not face any issues with Windows though
I can see there's a revert-22-master tag in docker hub, I tried it out and it seems like I don't get this error (at least after ~5 times). Although stopping the container is for some reason taking longer. Would you mind trying that tag @derMart ?
I tried the revert-22-master
tag. As this is undeterministic it is hard to tell, but from now only 2 startups problem does not appear (EDIT: will report back when I got some more experience). But I also experience that the container is taking much longer to shutdown. Tbh, that is pretty annoying ...
@delfer But this might be a hint that there is a regression going on between revert-22-master
and current release
@derMart @BenasB is this problem occurs with the latest image version? Whit Docker version do you use? Can you provide container output?
@delfer. I have the same problem. I'm using Docker Desktop 4.25.1 on a Mac with M1 chip. The latest version of the image. MacOS version is 14.1.1. Container output:
adduser: user 'user' in use
process has died, quitting
My docker compose file looks like this:
x-ftp-connection: &ftp-connection
USERS: $CORE__CDN_FTP_USER|$CORE__CDN_FTP_PASSWORD|/home/local
services:
storage:
image: delfer/alpine-ftp-server
environment: *ftp-connection
volumes:
- ./ftp_data:/home/local
ports:
- "21:21"
- "21000-21010:21000-21010"
Same here. Container dies randomly during startup. Running Macbook Pro M3 and Docker Desktop 4.27.0.
I have the problem, that the docker container sometimes! exits right after startup with exit code 0 showing only
ftp-server_1 | process has died, quitting
in the output but nothing else, no error message or anything. Restarting the container sometimes fixes the problem, very weird. Here is the configuration using docker-composewhere ${uid} is an environment variable.