camicroscope / Distro

Docker distribution of camicroscope and all its components
http://camicroscope.org
BSD 3-Clause "New" or "Revised" License
30 stars 147 forks source link

docker-compose -f caMicroscope.yml up command failed to run #206

Closed Ahmad-Bin-Zahid closed 1 year ago

Ahmad-Bin-Zahid commented 1 year ago

I simply ran the docker commad docker-compose -f caMicroscope.yml up which failed with the folllowing error message. Can someone please help me on this. Screenshot 2023-05-17 at 4 18 35 PM

birm commented 1 year ago

Thank you for the report!

Can you confirm that you are able to build the version in develop.yml?

That is, does docker-compose -f develop.yml build --no-cache loader work?

claudejin commented 1 year ago

I have met the same problem with @Ahmad-Bin-Zahid. So, tried what @birm said, and it works. Is it okay that I use the command docker-compose -f develop.yml up instead of docker-compose -f caMicroscope.yml up?

image

Ahmad-Bin-Zahid commented 1 year ago

@birm yes the command you shared ran successfully Screenshot 2023-05-19 at 4 18 29 PM

Ahmad-Bin-Zahid commented 1 year ago

I wanna deploy this somewhere for testing. How should I proceed considering the main command was not working?

birm commented 1 year ago

The docker base container of docker we used (stretch) is no longer supported. We just need to do a release in the near future.

In the meantime, depending on what you're testing, you might be able to use develop.yml; the main differences are that we're using pre-release code and have disabled most security features there.

Ahmad-Bin-Zahid commented 1 year ago

@birm also the docker-compose -f develop.yml up command is also failing to run with the folllowing error. Screenshot 2023-05-23 at 12 17 14 PM

Ahmad-Bin-Zahid commented 1 year ago

Well I kinda fixed the issue. I simply removed the existing container and again build the image. After that the command ran with no issues.

birm commented 1 year ago

I think the move away from depreciated ubuntu base images fixed this, please reopen if this issue persists.