docker-freescout icon indicating copy to clipboard operation
docker-freescout copied to clipboard

Container crashes

Open gerbenvandekraats opened this issue 1 year ago • 11 comments

Summary

When starting my container the container crashes on a /etc/cont-init.d error.

Steps to reproduce

Create the container based on version 1.17.35 or newer. Start the container and the error will show up in the logs.

What is the expected correct behavior?

No error message.

Relevant logs and/or screenshots

ERROR - Some initialization scripts haven't completed - All services are now halted The following scripts in '/etc/cont-init.d' did not pass their completion check: outage

Possible fixes

It looks to me this build contains a file that shouldn't be there: install/etc/cont-init.d/outage

gerbenvandekraats avatar Oct 09 '23 07:10 gerbenvandekraats

I confirm, after updating the container, freescout does not start, in the logs:

ERROR - Some initialization scripts haven't completed - All services are now halted **** **** - The following scripts in '/etc/cont-init.d' did not pass their completion check ****

и

Image: tiredofit/freescout Repository/Issues/Support: https://github.com/tiredofit/docker-freescout/ /etc/cont-init.d/outage: line 1: look: not found /etc/cont-init.d/outage: line 2: crhased: not found

yabloky avatar Oct 09 '23 09:10 yabloky

Same here

MyWay avatar Oct 09 '23 09:10 MyWay

I uninstalled latest and installed this version - php8.2-1.17.34, everything works, all modules updated.

yabloky avatar Oct 09 '23 09:10 yabloky

I can confirm ⬆️ @yabloky 's solution. I previously used php8.2 (which defaults to php8.2-1.17.36 at the moment of this writing) and is now broken with above error. I can also confirm php8.2-1.17.35 is broken.

SpikySpam avatar Oct 09 '23 10:10 SpikySpam

Other temporary solution is to bash into your container and delete the file 'outage' by hand from the directory '/etc/cont-init.d'.

gerbenvandekraats avatar Oct 09 '23 12:10 gerbenvandekraats

Same problem like others ... XXXX.35 - broken, XXXX.36 - broken ... backstep to XXXX.34 .

marek94901 avatar Oct 09 '23 14:10 marek94901

Same here. deleting the file outage in the container works.

kitefreakk avatar Oct 09 '23 14:10 kitefreakk

Sorry, a text file snuck itself into that directory somehow while comitting. I've cleaned things up - but best to just pull 1.17.37 now..

tiredofit avatar Oct 09 '23 15:10 tiredofit

Hey no worries,

Seems like a great product!

I need some more tests dough. then we can maybe use it. Depends on the Modules. I have just asked my boss to spend a li0ttle money...

Anyway, verzio .37 seems to spin up again.

Got me a bunch of FATAL messages, but it seems to work:

image

SpikySpam avatar Oct 09 '23 18:10 SpikySpam

I don't knows where that FATAL error comes from, but I guess, I could be mistaken, you are willing to push an image a little too soon?

Relax dude, ... I'm testing for you...

SpikySpam avatar Oct 09 '23 19:10 SpikySpam

PS. If you need something quickly tested on a windows Machine. you can ask me. I'm really am searching for a long time for a good and cheap HelpDesk. This seems to be it. But not with a screw-up like this little mistake. Can I help?

SpikySpam avatar Oct 09 '23 19:10 SpikySpam