8000 Bug: Wekan - Synology · Issue #3874 · wekan/wekan · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Bug: Wekan - Synology #3874

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Closed
marek94901 opened this issue Jun 23, 2021 · 18 comments
Closed

Bug: Wekan - Synology #3874

marek94901 opened this issue Jun 23, 2021 · 18 comments

Comments

@marek94901
Copy link

Hi,

wekan doesn't work for us today. I don't know what caused the defect, but I noticed the download of a new image via watchtower. We use docker on our synology nas.

wekan: v5.35
mongo db: 4.4.6
synology docker app: 20.10.3.-0552

Here is a list of logs:

ReferenceError: describe is not defined
at module (server/lib/utils.tests.js:6:1)
at fileEvaluate (packages/modules-runtime.js:336:7)
at Module.require (packages/modules-runtime.js:238:14)
at require (packages/modules-runtime.js:258:21)
at /build/programs/server/app/app.js:27729:1
at /build/programs/server/boot.js:401:38
at Array.forEach ()
at /build/programs/server/boot.js:226:21
at /build/programs/server/boot.js:464:7
at Function.run (/build/programs/server/profile.js:280:14)
at /build/programs/server/boot.js:463:13

Thanks.
@marek94901 marek94901 changed the title Wekan - Synology Bug: Wekan - Synology Jun 23, 2021
@xet7
Copy link
Member
xet7 commented Jun 24, 2021 •
edited
Loading

@marek94901

  1. Stop wekan-app and remove it:
docker stop wekan-app
docker rm wekan-app

2a) Try with this image:

image: quay.io/wekan/wekan:v5.35

2b) or this image:

image: wekanteam/wekan:v5.35

If you use docker commands, use something like this:

docker run -d --restart=always --name wekan --link "wekan-db:db" -e "WITH_API=true" -e "MONGO_URL=mongodb://wekan-db:27017/wekan" -e "ROOT_URL=http://192.168.1.200:2000" -p 2000:8080 quay.io/wekan/wekan:v5.35

If you use instead use docker-compose, after changing docker-compose.yml do:

docker-compose up -d

@Major2828
Copy link
Major2828 commented Jun 24, 2021 •
edited
Loading

Had same error, changing image to image: quay.io/wekan/wekan helped me.
In the same time I also updated the docker.compose.yml (update mongoDB to 4.4 and update the start command for mongoDB) but I think it has nothing to do with mongoDB

@xet7
Copy link
Member
xet7 commented Jun 24, 2021

@Major2828

I don't recommend running that latest tag like in your example, because there are In Progress incomplete features like Shared Templates. I recommend running release tags like v5.35 like above in my example.

@Major2828
Copy link

@xet7 thank you for your response, i thought the latest tag would update only if a release happend?
So actual latest would be 5.35 or do i missanderstand something?

@xet7
Copy link
Member
xet7 commented Jun 24, 2021

@Major2828

No. Latest is newest git commit at master branch, and it can sometimes be broken, like unstable/devel. Wekan has only one branch, master. It builds every time there is new commit. Commits are here:
https://github.com/wekan/wekan/commits/master

Releases are when some specific release has numbered release tag, like v5.35. When release tag is added, then new Snap/Sandstorm/Bundle etc versions are built.

@Major2828
Copy link

@xet7 oh that is very interesting thank you very much, i will change it :)

@marek94901
Copy link
Author

Hi, thank you very much for the advice. I was desperate in the morning, so I tried several methods and the last thing I could think of was to use the old image in version 5.35. This version works.

@xet7 xet7 closed this as completed Jun 24, 2021
xet7 added a commit that referenced this issue Jun 24, 2021
@xet7
Note: With Docker, please don't use latest tag. Only use release tags.
f18a57b 
See #3874

Thanks to xet7 !
xet7 added a commit that referenced this issue Jun 24, 2021
@xet7
Note: With Docker, please don't use latest tag. Only use release tags.
c4cea9e 
See #3874

Thanks to xet7 !
@gpalyu
Copy link
gpalyu commented Jun 30, 2021

Can someone who has applied the fix tell me if it's possible to change the tag from latest to release in the Synology UI? I don't see that tag listed when I download a new image, but I can download version 5.35 specifically. I don't think there's a great way to change versions if I do 5.35 without updating things manually to a new version?

@xet7
Copy link
Member
xet7 commented Jun 30, 2021

@gpalyu

I don't know how you add or remove docker images in Synology UI, I don't have Synology.

With Docker, it's done this way: #3874 (comment)

You see newest Wekan version from https://wekan.github.io/ above Download button, currently newest and greatest is Wekan v5.36, it includes all recent fixes.

I would think you remove previous wekan-app container and download newest with tag v5.36

@xet7
Copy link
Member
xet7 commented Jun 30, 2021

You should keep your existing wekan-db (mongodb) container, and also have daily backups

@gpalyu
Copy link
gpalyu commented Jul 12, 2021

Thank you @xet7 I figured out how to do this so I can run on a stable version all the time now.

@xet7 xet7 mentioned this issue Sep 1, 2021
Closed
@luistiktok luistiktok mentioned this issue Sep 16, 2021
Closed
@styxlcx styxlcx mentioned this issue Sep 22, 2021
Closed
@eriky
Copy link
eriky commented Sep 28, 2021

Most, if not all, open-source projects point the latest tag to the latest release. I've never seen this being used in this way. I feel it would be better to conform to that de-facto standard instead of needing to warn people about this. This is probably going to be an issue for many users to come if left unchanged.

@xet7
Copy link
Member
xet7 commented Sep 28, 2021

@eriky

Latest tags do point to latest releases.

@danst0 danst0 mentioned this issue Oct 9, 2021
Closed
@ufalke ufalke mentioned this issue Oct 11, 2021
Open
@modem7
Copy link
modem7 commented Jan 27, 2022 •
edited
Loading

Most, if not all, open-source projects point the latest tag to the latest release. I've never seen this being used in this way. I feel it would be better to conform to that de-facto standard instead of needing to warn people about this. This is probably going to be an issue for many users to come if left unchanged.

To echo @eriky, typically in open source projects that I've come across, the latest tag is the latest stable release.

They then have tags for development/nightly etc where those releases are published to via the CI/CD system.

@xet7
Copy link
Member
xet7 commented Jan 27, 2022

@modem7

I already fixed that at 2021-11-12. When releasing, I push to release tags and latest tags:

@gohrner
Copy link
gohrner commented Oct 2, 2022

@modem7
I already fixed that at 2021-11-12. When releasing, I push to release tags and latest tags:

Maybe the README.md should be adjusted then?

It still reads:

Docker: Please only use Docker release tags
Note: With Docker, please don't use latest tag. Only use release tags. See #3874

As I understood the your comment here, the latest tag should now be safe.

xet7 added a commit that referenced this issue Oct 3, 2022
@xet7
Updated README.md about Docker: You can use latest tag to get newest …
fc28b6c 
…release tag.

Thanks to gohrner and xet7 !

Fixes #3874
@Entepotenz Entepotenz mentioned this issue Feb 25, 2023
Merged
@C0rn3j
Copy link
Contributor
C0rn3j commented Oct 1, 2023

@xet7 While you did fix the above in README.md, it's still hanging around in https://hub.docker.com/r/wekanteam/wekan

image

@xet7
Copy link
Member
xet7 commented Oct 1, 2023

@C0rn3j

I updated Docker Hub readme.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
8 participants
@xet7 @eriky @C0rn3j @modem7 @Major2828 @gohrner @gpalyu @marek94901
0