Docker setup issues about debattons HOT 6 CLOSED

OK I think I know why, it's due to the fact that we're using .m2 and .npm folders in your $HOME.

So docker will create such folders if they don't exist and create them with the user root so they become unusable for the debattons:dev image which uses your own $UID & $GID to run.

You should be able to fix this problem giving the rights to your own user to those 2 folders.
I think we should add a chown command in docker/cmd.sh :)

from debattons.

Thanks I'll try these two fixes tomorrow 😉

from debattons.

Mmmh I've tested the parameter and the bug is still here:

+ sudo -E yarn global add @angular/[email protected] --network-concurrency 1
yarn global v1.3.2
[1/4] Resolving packages...
error An unexpected error occurred: "https://registry.yarnpkg.com/asn1: ETIMEDOUT".
info If you think this is a bug, please open a bug report with the information provided in "/usr/local/share/.config/yarn/global/yarn-error.log".
info Visit https://yarnpkg.com/en/docs/cli/global for documentation about this command.
ERROR: Service 'debattons' failed to build: The command '/bin/sh -c setup.sh --no-debattons-git-copy' returned a non-zero code: 1

from debattons.

Perhaps that it is also linked to this yarn issue: yarnpkg/yarn#944 (comment), which seems to be fixed by adding --network-concurrency 1 to yarn commands.

from debattons.

@Betree I've just changed the Docker execution architecture, so try to remove all temporary files (or delete all the project & re-clone the repo) and retry ./docker/cmd.sh build-and-run.
I've encountered the Cannot find module '@angular-devkit/core' problem and fixed it by passing to the latest version of angular-cli thanks to angular/angular-cli#9307 (comment)

from debattons.

Yep it did the trick 🙂

from debattons.