Docker on different obrabatyvat team?

Hi All !
The question is simple, is Jenkins which is standard when you upgrade a branch cecchet update and build the project. Build essentially turns the command list. Now on the same team all the falls, namely, when after
Jenkins updates the directory:
docker exec -i git workspace-C /var/www// pull
after going
docker exec -i workspace composer install -d /var/www/

here the problem, the team sent in a container from the outside, it falls with error:

node-zopfli@2.0.2 install /var/www/staging/laravel/node_modules/node-zopfli
> node-pre-gyp install --fallback-to-build

node-pre-gyp ERR! Tried to download(403): 
node-pre-gyp ERR! Pre-built binaries not found for node-zopfli@2.0.2 and node@0.10.29 (node-v11 ABI) (falling back to source compile with node-gyp) 
make: Entering directory '/var/www/staging/laravel/node_modules/node-zopfli/build'
 CXX(target) Release/
In file included from ../src/zopfli-binding.h:5:0,
 from ../src/
../../nan/nan.h:324:47: error: 'REPLACE_INVALID_UTF8' is not a member of 'v8::String'
 static const unsigned kReplaceInvalidUtf8 = v8::String::REPLACE_INVALID_UTF8;

I understand that he needs to put libo zopfli, and it is not available, but then why when I go to the container and run the same command - the project is going without any problems ?
Today removed libo which was pulled up zopfli - the problem is not gone. I do not know where to dig.
July 2nd 19 at 13:07
1 answer
July 2nd 19 at 13:09
The solution was simple, the problem was discovered after it turned out that my contenere is two versions of node
this variant showed the same version
docker exec -i workspace node --version
docker exec -i which the node workspace

and inside of kontenera other. It became clear that when you run a command called different node. After inventory Dockerfile and rebuild the base image with the correct versions and paths - the problem disappeared

Find more questions by tags Docker