Docker script does not default arguments correctly about wekan HOT 15 CLOSED

@DMCShep

What versions of docker-compose and docker are your running?

from wekan.

Running into the same issue

root@KS-Docker-01:~/wekan# /usr/local/bin/docker-compose -v
docker-compose version 1.8.1, build 878cff1

root@KS-Docker-01:~/wekan# docker -v
Docker version 1.13.0, build 49bf474

root@KS-Docker-01:~/wekan# uname -a
Linux KS-Docker-01 4.8.0-34-generic #36-Ubuntu 

Changing:

ENV BUILD_DEPS="wget curl bzip2 build-essential python git ca-certificates"
ENV GOSU_VERSION=1.10
ARG NODE_VERSION=v0.10.48
ARG METEOR_RELEASE=1.3.5.1
ARG NPM_VERSION=3.10.10
ARG ARCHITECTURE=linux-x64
ARG SRC_PATH=./

To:

ENV BUILD_DEPS="wget curl bzip2 build-essential python git ca-certificates"
ENV GOSU_VERSION=1.10
ENV NODE_VERSION=v0.10.48
ENV METEOR_RELEASE=1.3.5.1
ENV NPM_VERSION=3.10.10
ENV ARCHITECTURE=linux-x64
ENV SRC_PATH=./

Got me a little further in the process only the fail when installing Meteor with a bunch these errors:

tar: .meteor/packages/babel-compiler: Directory renamed before its status could be extracted

Either my workaround is wrong or there's more fixing needed before this is going to build.

from wekan.

@Aeny202
ARG should work just as well as ENV with docker so I don't think this is an issue with the Dockerfile.

In terms of the other error, can you specifiy your system architecture?

echo -n $(uname -s | tr '[:upper:]' '[:lower:]'); echo -n "-"; echo $(uname -p | tr '[:upper:]' '[:lower:]');

or just

uname -a and include all the info.

from wekan.

I experience the same error

tar: .meteor/packages/babel-compiler: Directory renamed before its status could be extracted

I am using Windows 10

$ uname -a
MSYS_NT-10.0 mycomputer 2.6.1(0.306/5/3) 2017-01-14 09:41 x86_64 Msys

$ docker -v                                                              
Docker version 1.13.0, build 49bf474                                        

$ docker-compose -v                                                      
docker-compose version 1.10.0, build 4bd6f1a0                            

Possibly related:
docker/hub-feedback#727
moby/moby#19647

from wekan.

@centigrade-thomas-becker
That was some very useful information there. Thanks!
The error seems to be described well at this link https://github.com/docker/docker/issues/19647#issuecomment-256794331.
I'd be inclined to say that this is an issue relatively unrelated to wekan and there seems to be someone working on a fix.

from wekan.

Since the problem seems to be related to the overlay storage driver, I configured my docker daemon to use another storage.

Initially it was using overlay2. When I switched to overlay to aufs the tar-related error disappeared, and I got one step further. The different storage drivers used by Docker are documented here.

But now I have another error:

Downloading Meteor distribution

Meteor 1.3.5.1 has been installed in your home directory (~/.meteor).

Now you need to do one of the following:

  (1) Add "$HOME/.meteor" to your path, or
  (2) Run this command as root:
        cp "/home/wekan/.meteor/packages/meteor-tool/1.3.5_1/mt-os.linux.x86_64/scripts/admin/launch-meteor" /usr/bin/meteor

Then to get started, take a look at 'meteor --help' or see the docs at
docs.meteor.com.
npm ERR! Linux 4.9.4-moby
npm ERR! argv "node" "/home/wekan/.meteor/packages/meteor-tool/.1.3.5_1.1sksnpz++os.linux.x86_64+web.browser+web.cordova/mt-os.linux.x86_64/dev_bundle/bin/npm" "install" "--save" "xss"
npm ERR! node v0.10.46
npm ERR! npm  v3.10.5
npm ERR! path /home/wekan/app/node_modules/xss
npm ERR! code EXDEV
npm ERR! errno 52

npm ERR! EXDEV, rename '/home/wekan/app/node_modules/xss'
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     <https://github.com/npm/npm/issues>

npm ERR! Please include the following file with any support request:
npm ERR!     /home/wekan/app/npm-debug.log

The cause of the "EXDEV rename" error seems to be that both aufs and overlay don't support rename operations:

• https://docs.docker.com/engine/userguide/storagedriver/overlayfs-driver/#/overlayfs-compatibility
• https://docs.docker.com/engine/userguide/storagedriver/aufs-driver/#/renaming-directories-with-the-aufs-storage-driver

from wekan.

@centigrade-thomas-becker

So my understanding is

• overlay storage method has an issue pending resolution

• aufs has this issue 9863

Do you mind sending me a link to the steps needed to change docker to use aufs storage?

I'll see later about resolving this once I get the bug on my own system.

Thanks.

from wekan.

In order to select a different storage driver you have to edit the config file for the docker daemon, and then restart the daemon.

I am using Windows 10 so I just used the docker icon in the system tray (Settings => Daemon => Advanced) to set my driver to:

{
  "storage-driver": "aufs"
}

You can check your current storage driver with docker info

Also, take note that once you change your storage driver all your current containers and images won't be available anymore. At least not until you switch back to your previous storage driver.

from wekan.

Chiming in: I'm in the process of setting up a new server for testing the install process. The one I used before was shared with some other sites and ran into issues with insufficient resources as a result. It was the latest version of docker and docker-compose when I ran into the issue above.

That said, It sounds like you guys are well on your way to working out the kinks on your own, even if it's a docker bug and not a wekan bug. Keeping tabs on this issue.

If it helps, I was running Ubuntu 16.04 or 16.10 before (don't recall which), but will test with 16.10 when server setup is done. Taking a while because I'm generating a "baseline" image to revert back to after each test to make a sort of "clean slate".

from wekan.

I finally got it working.

First, I tried to switch from npm to yarn to avoid the EXDEV error during the step gosu wekan /home/wekan/.meteor/meteor npm install --save xss && \. But yarn as a meteor command is not supported in meteor 1.3, and I did not want to open that can of worms.

Once wekan supports meteor 1.4 we should be able to use yarn as described here.

So I ended up removing the line gosu wekan /home/wekan/.meteor/meteor npm install --save xss && \ altogether, and it seems that Wekan works fine even without it. Since a security feature is now missing (protection against cross site scripting) this is obviously not a viable solution. But at least it is running now.

from wekan.

Ok, great work @centigrade-thomas-becker. Useful information there.

In that case, my suggestion for the Dockerfile then is that we wait until wekan is updated to > meteor 1.4.1.3 and then a PR can be made to switch to yarn.

I would think upgrading wekan to meteor 1.4 is a high priorty, @xet7 ?

from wekan.

@stephenmoloney

Is this default arguments issue still a problem? When I yesterday merged Wefork to Wekan, Docker Hub did build working docker image that has still gosu commands in it:
https://hub.docker.com/r/mquandalle/wekan/tags/
https://hub.docker.com/r/mquandalle/wekan/~/dockerfile/

I did run Wekan with:

docker run -d --restart=always --name wekan-db mongo:3.2.11

docker run -d --restart=always --name wekan --link "wekan-db:db" -e "MONGO_URL=mongodb://db" -e "ROOT_URL=http://localhost:8080" -p 8080:80 mquandalle/wekan:latest

Sorry maybe I just didn't read all messages in this post more carefully what's the exact problem. Please write me a short TL;DR version.

Anyway I still have pull requests to integrate and more stuff to move from Wefork to Wekan (issues, wiki etc) so I don't know how high priority is upgrading yet, I'm trying to keep up with speed that Wekan community is moving.

from wekan.

RE: Is this default arguments issue still a problem?

• No, ENV or ARG work equally well. This issue may arise if the user has an older version of docker or docker-compose which does not support ARG.

• This thread has morphed into a different conversation whereby on certain linux systems and storage backends, the command gosu wekan /home/wekan/.meteor/meteor npm install --save xss might be a problem for the aufs storage backend. This can be fixed by upgrading meteor to version 1.4 and using yarn instead of meteor instead.

• On the overlay-fs storage backend, there might arise another issue: https://github.com/docker/docker/issues/19647

• Both of these issues are not really wekan related as far as I can tell.

In short, my conclusion is that once wekan is upgraded to version of meteor 1.4 +, that we move from npm to yarn to avoid some of these issues. I will create a new issue for this now.

Perhaps, we can close this issue now, the discussion has moved off the title anyways.
@xet7

from wekan.

Closing issue for reasons described above

from wekan.

@xet7
I've made a few changes in my directory and I'm actually noticing this issue brought up by @DMCShep now which I couldn't replicate before this. So Yes, in fact, I think @DMCShep is right about the ARG being a problem.

The good news is I've come up with a fix, I'll make a pull request to wekan/wekan for it soon.

from wekan.