Docker hub Calendso not working about docker

[krumware]

moving on to this now that the build is stable

[krumware]

Thanks for re-opening!
(linking closed issue here: #2)

[kelvinalfaro]

@dotesfera with Changes from @krumware in other issues I was able to get my fork to work. I also got the actions auto builds to work for dockers images - docker pull ghcr.io/kelvinalfaro/docker:main

[PeerRich]

hey everyone, we just made a dedicated GitHub Team for docker, #32

anyone wants to join and help us get Docker Hub fixed?

[cyango]

When is this going to be available on docker Hub?

[cyango]

@dotesfera with Changes from @krumware in other issues I was able to get my fork to work. I also got the actions auto builds to work for dockers images - docker pull ghcr.io/kelvinalfaro/docker:main

Using portainer with your fork, it gives this error, any clue?

[krumware]

I don't use portainer, but you could try killing the lines in the docker-compose which include volume references

[cyango]

Hum, using your suggestion and deploying the stack via portainer gives "Unable to deploy error"... so I think having this on docker hub would be life saving...

[krumware]

I'm on the outside looking in but being on docker hub likely would not change your issue. It sounds like there is an issue with your configuration of the deployment of the image and not necessarily the image itself.

From past experience on other platforms, it may be that portainer does not recursively clone the submodule by default, so the calendso folder might not be populated. If so the build will certainly fail.

Is there any sort of logging beyond the error modal?

[emrysal]

Docker hub circumvents docker-compose I suppose, so maybe Portainer would no longer use that file at all?

[cyango]

Where can I see Portainer logs on a failed stack deployment?

Is there any possibility to add this to docker hub? Because I could use my Synology docker to easily install this...

[cyango]

Any news on this?

[cyango]

moving on to this now that the build is stable

Is there any estimation when this is solved?

[krumware]

@dotesfera this is now building and pushing to the public image

[ovizii]

I would prefer using an image from dockerhub rather than building my own according to the instructions here so I am wondering, is this the image which is being maintained and suggested to use?
There are a couple of others which also seem up-to-date hence my question.

=> https://hub.docker.com/r/calendso/calendso
(Btw. I noticed this one also needs to be git cloned and then built, right? So, no usage right off the bat?)

[PeerRich]

I haven't used docker in a while but https://hub.docker.com/r/calendso/calendso should be ready to go @krumware right?

[ovizii]

maybe the instructions just have not been updated? I checked https://hub.docker.com/r/calendso/calendso and it still says:

[krumware]

@ovizii there are limitations being talked about and tracked here: #56

The issue is that Calendso bakes variables into a static build, which forces us to have some form of build process in addition to the container run. There is another thread in calendso/calendso which talks about it as well. Because of the static build, we are losing some runtime convenience in favor of render speed, even though there are tools provided in next.js for runtime variables. (not my decision)

I'm testing a workaround outlined in the thread linked above

[krumware]

For localhost usage and demo, the dockerhub option works out of the box. For production configurability at runtime, we're working through that

[ovizii]

@krumware thanks, I had read a couple of topics here and I don't mind building the image myself. It seems I misread a couple of replies in this thread which led me to believe this was already no longer necessary.
I'll give it a go, perfectly happy to see how it all works.

[krumware]

I'm working on adding a quick conditional to the start script to run the dev server at runtime, which could give us configurability we're looking for. Testing now

[cyango]

Made it work finally using docker hub, thank you!