Closed sendit2me closed 7 years ago
hmm.. that may be a build problem. I'll take a look later today.
What version of the container are you using?
Any news on that ? I have the same error. Thank you
I'm not able to reproduce it locally...
What version of the container are you using? What browser and browser version are you using?
Happens to me as well, i will post more details how to reproduce the issue later.
haphan@hpbookpro:~$ docker --version
Docker version 17.03.1-ce, build c6d412e
haphan@hpbookpro:~$ docker-compose --version
docker-compose version 1.11.2, build dfed245
haphan@hpbookpro:~$ docker images | grep para
parabuzzle/docker-registry-ui latest 3e51ea678704 3 weeks ago 980 MB
Command was used to launch
docker run -d \
-p 8123:80 \
-e REGISTRY_HOST=registry.example.com \
-e REGISTRY_PORT=443 \
-e REGISTRY_PROTO=https \
-e REGISTRY_SSL_VERIFY=true \
-e REGISTRY_USERNAME=xxxx \
-e REGISTRY_PASSWORD=xxxx \
-e USERNAME=admin \
-e PASSWORD=xxxxx \
parabuzzle/docker-registry-ui:latest
I am using Chrome on Mac Sierra.
Hope this helps you to reproduce the issue @parabuzzle
Okay, I believe something wrong with the docker image published in store.docker.com
It works when I rebuild the docker image locally. I am putting steps here in case anyone need it. @xavierdavidgarcia
$ git clone https://github.com/parabuzzle/craneoperator.git && cd craneoperator
$ gem install httparty memoist
$ npm install && npm install webpack
$ rake build
$ docker build -t registry-ui:latest .
docker run -d \
-p 8123:80 \
-e REGISTRY_HOST=registry.example.com \
-e REGISTRY_PORT=443 \
-e REGISTRY_PROTO=https \
-e REGISTRY_SSL_VERIFY=true \
-e REGISTRY_USERNAME=xxxx \
-e REGISTRY_PASSWORD=xxxx \
-e USERNAME=admin \
-e PASSWORD=xxxxx \
registry-ui:latest
I am also getting this on the latest version, though version 2.1.3 works ok :)
can you check version 2.1.5 please?
had the prop-types issue yesterday with 2.1.4
as well. 2.1.5
seem to resolve that issue 👍
Problem was in the webpack build.
I keep getting
Uncaught Error: Cannot find module "prop-types"
when starting the container, and attaching to a local registry, have tried a number of settings.