How to switch from validator/validator to ghcr.io/validator/validator

[ptmkenny]

I've been using Lando with validator/validator for a couple years, but today, when I rebuild my local development environment, I couldn't pull from validator/validator. I checked the documentation, and it seems that the docker image is now at ghcr.io/validator/validator.

I downloaded the new image but it no longer works.

Here's my original lando config:

  vnu:
    # https://github.com/lando/lando/issues/2731
    type: compose
    ssl: true
    sslExpose: false
    services:
      image: validator/validator:20.6.30
      command: java -cp ~/vnu.jar nu.validator.servlet.Main 8888
      ports:
        - '8888:8888'

And here's what I tried with the new image:

  vnu:
    # https://github.com/lando/lando/issues/2731
    type: compose
    ssl: true
    sslExpose: false
    services:
      image: ghcr.io/validator/validator:latest
      command: java -cp ~/vnu.jar nu.validator.servlet.Main 8888
      ports:
        - '8888:8888'

Any ideas about how to get this working again would be much appreciated.

[sideshowbarker]

Thanks for reporting this.

Can you be specific about what exactly doesn’t work? What is the exact error message that gets reported? What exactly fails to happen?

I’m not familiar with Lando, so I’m not sure how useful I can be with trying to troubleshoot any Lando-specific failures.

But what I can say is that things work as expected when the docker image is run this way:

docker run ghcr.io/validator/validator

For example:

$ docker run ghcr.io/validator/validator
Unable to find image 'ghcr.io/validator/validator:latest' locally
latest: Pulling from validator/validator
b49b96595fd4: Pull complete
bb771d6dc9a1: Pull complete
ed1e270b969c: Pull complete
e0a609cbfa1b: Pull complete
60fc7912818f: Pull complete
7be0971cd4db: Pull complete
Digest: sha256:0efb4fa7fb5d3258b42f21fbb730468c3862b466a1fecbb9600db62ac3eb9ec7
Status: Downloaded newer image for ghcr.io/validator/validator:latest
Picked up JAVA_TOOL_OPTIONS:
nu.validator.servlet.VerifierServletTransaction - Starting static initializer.
nu.validator.servlet.VerifierServletTransaction - Reading miscellaneous properties.
nu.validator.servlet.VerifierServletTransaction - Starting to loop over config file lines.
nu.validator.servlet.VerifierServletTransaction - Finished reading config.
nu.validator.servlet.VerifierServletTransaction - Converted config to arrays.
nu.validator.servlet.VerifierServletTransaction - Prepared namespace array.
nu.validator.servlet.VerifierServletTransaction - Parsed doctype numbers into ints.
nu.validator.servlet.VerifierServletTransaction - The cache path prefix is: null
nu.validator.servlet.VerifierServletTransaction - Parsing set up. Starting to read schemas.
nu.validator.servlet.VerifierServletTransaction - Will load schema: http://s.validator.nu/html5.rnc
nu.validator.servlet.VerifierServletTransaction - Will load schema: http://s.validator.nu/html5-all.rnc
nu.validator.servlet.VerifierServletTransaction - Will load schema: http://s.validator.nu/xhtml5.rnc
nu.validator.servlet.VerifierServletTransaction - Will load schema: http://s.validator.nu/xhtml5-all.rnc
nu.validator.servlet.VerifierServletTransaction - Will load schema: http://s.validator.nu/svg-xhtml5-rdf-mathml.rnc
nu.validator.servlet.VerifierServletTransaction - Schemas read.
nu.validator.servlet.VerifierServletTransaction - Reading spec.
nu.validator.servlet.VerifierServletTransaction - Spec read.

Checker service started.

[ptmkenny]

Thanks for responding.

When I start lando to bring up all the containers (lando provides a local dev environment), the ghcr.io/validator/validator:latest container fails to load.

It was working with validator/validator:20.6.30.

I'll post the error below.

Since the container has been downloaded successfully, I think the problem may be with the command java -cp ~/vnu.jar nu.validator.servlet.Main 8888.

What I was expecting with this command (and what happened with the previous version) was that I would get a locally hosted webserver with the validation service so that I could run validation against my webserver container. Has the command changed? I checked the docs but it seemed to be the same.

Here's the lando error for reference:

Starting myapp_vnu_1 ... done
myapp 22:28:41 ERROR ==>  message=, stack=Error
    at /snapshot/lando/build/cli/lib/shell.js
From previous event:
    at Shell.sh (/snapshot/lando/build/cli/lib/shell.js)
    at Object.dc (/snapshot/lando/build/cli/lib/bootstrap.js)
    at compose (/snapshot/lando/build/cli/lib/bootstrap.js)
From previous event:
    at /snapshot/lando/build/cli/lib/router.js
    at processImmediate (internal/timers.js:456:21)
From previous event:
    at Object.run (/snapshot/lando/build/cli/lib/router.js)
    at run (/snapshot/lando/build/cli/lib/engine.js)
    at /snapshot/lando/build/cli/lib/router.js
From previous event:
    at Object.eventWrapper (/snapshot/lando/build/cli/lib/router.js)
    at Engine.engineCmd (/snapshot/lando/build/cli/lib/engine.js)
    at Engine.run (/snapshot/lando/build/cli/lib/engine.js)
    at /snapshot/lando/build/cli/plugins/lando-core/app.js
From previous event:
    at AsyncEvents.<anonymous> (/snapshot/lando/build/cli/plugins/lando-core/app.js)
    at AsyncEvents.handle (/snapshot/lando/build/cli/lib/events.js)
    at /snapshot/lando/build/cli/lib/events.js
From previous event:
    at AsyncEvents.emit (/snapshot/lando/build/cli/lib/events.js)
    at /snapshot/lando/build/cli/lib/app.js
From previous event:
    at App.start (/snapshot/lando/build/cli/lib/app.js)
    at Object.run (/snapshot/lando/build/cli/plugins/lando-core/tasks/start.js)
From previous event:
    at /snapshot/lando/build/cli/lib/cli.js
From previous event:
    at Object.handler (/snapshot/lando/build/cli/lib/cli.js)
    at Object.runCommand (/snapshot/lando/build/cli/node_modules/yargs/lib/command.js:238:44)
    at Object.parseArgs [as _parseArgs] (/snapshot/lando/build/cli/node_modules/yargs/yargs.js:1063:30)
    at Function.get [as argv] (/snapshot/lando/build/cli/node_modules/yargs/yargs.js:1004:21)
    at Cli.init (/snapshot/lando/build/cli/lib/cli.js)
    at Cli.run (/snapshot/lando/build/cli/lib/cli.js)
    at Object.<anonymous> (/snapshot/lando/build/cli/bin/lando.js)
    at Module._compile (pkg/prelude/bootstrap.js:1433:22)
    at Object.Module._extensions..js (internal/modules/cjs/loader.js:1156:10)
    at Module.load (internal/modules/cjs/loader.js:984:32)
    at Function.Module._load (internal/modules/cjs/loader.js:877:14)
    at Function.runMain (pkg/prelude/bootstrap.js:1488:12)
    at internal/main/run_main_module.js:17:47, __stackCleaned__=true

[sideshowbarker]

Has the command changed?

Yes, the command has changed. The current image doesn’t use vnu.jar at all — instead it uses a Linux binary.

See this line of the Dockerfile:

validator/Dockerfile

Line 36 in e68bf0a

CMD ["./vnu-runtime-image/bin/java", "-m", "vnu/nu.validator.servlet.Main", "8888"]

What that means is, rather than running java -cp ~/vnu.jar nu.validator.servlet.Main 8888, the equivalent is:

vnu-runtime-image/bin/java -m vnu/nu.validator.servlet.Main 8888

[sideshowbarker]

@ptmkenny Did the vnu-runtime-image/bin/java -m vnu/nu.validator.servlet.Main 8888 invocation work for you? Can we consider this resolved? If, I think you can actually mark this as answered?

[ptmkenny]

@sideshowbarker Thanks, I'm still trying to figure out how to do this in lando-- I can't use the command as is. I will update if I figure out how to get it working in lando, but I'll go ahead and mark this as answered since this is a lando issue now.

[sideshowbarker]

OK, thanks — I’m happy to help further with troubleshooting it, in any way I can (as I said, I don’t know lando, but if, e.g., it turns out there’s something I could change in the Dockerfile to make the lando integration easier, I’d be happy to)