The image was updated to use an entrypoint, so you can drop "$PWD:/tmp/json
jboss/keycloak:1.8.1.Final \ /opt/jboss/keycloak/bin/standalone.sh", and
just run it with:
docker run -it --rm -v -b 0.0.0.0
-Dkeycloak.migration.action=import
-Dkeycloak.migration.provider=singleFile
-Dkeycloak.migration.file=/tmp/json/yyy.json
-Dkeycloak.migration.strategy=OVERWRITE_EXISTING
On 12 February 2016 at 15:03, Tim Dudgeon <tdudgeon.ml(a)gmail.com> wrote:
I've hit an issue with import. The command I used to use to
import a
realm with 1.7.0 now gives an error with 1.8.1, but from reading the
docs all the options seem to be valid. Could someone point to what has
changed?
The command I'm using is
/opt/jboss/keycloak/bin/standalone.sh -b 0.0.0.0
-Dkeycloak.migration.action=import
-Dkeycloak.migration.provider=singleFile
-Dkeycloak.migration.file=/tmp/json/yyy.json
-Dkeycloak.migration.strategy=OVERWRITE_EXISTING
Or to be more correct, I'm doing this in Docker, and it can be
reproduced like this:
docker run -it --rm -v $PWD:/tmp/json jboss/keycloak:1.8.1.Final
/opt/jboss/keycloak/bin/standalone.sh -b 0.0.0.0
-Dkeycloak.migration.action=import
-Dkeycloak.migration.provider=singleFile
-Dkeycloak.migration.file=/tmp/json/yyy.json
-Dkeycloak.migration.strategy=OVERWRITE_EXISTING
which tells me that I've specified an invalid option. It works fine if I
use the 1.7.0.Final image.
Tim
_______________________________________________
keycloak-user mailing list
keycloak-user(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/keycloak-user