anchor.diff:  This post explains how we execute Arquillian tests into a Docker container, so we'll talk about :
   
   * {uri-docker-asciidoctorj-github}[docker-asciidoctorj], the dedicated project on Asciidoctor organization
  +* {uri-asciidoctor-dockerhub}[the Asciidoctor organization on Docker Hub],
   * {uri-arquillian-cube-github}[Arquillian Cube], the Arquillian extension that can be used to manager Docker containers from Arquillian.
   * {uri-jboss-wildfly-docker}[the WildFly docker image] from JBoss
   ====
  
positive.code: If you do it, I'd love to have your feedbacks so feel free to add a comment here, on the discussion list or on the GitHub project. +
  We are waiting for PR :)
  
  == Asciidoctor has is own official registry on Docker Hub
  
  The good news here is that the asciidoctor project now have an easy way to test if the future versions will be compatible with this architecture.
  The other good news is that the
  
negative.code: :toc2:
  :toc-placement: preamble
  :toc-title: Table of Contents
  :toclevels: 4
  :source-highlighter: coderay
  :linkattrs:
  :sectanchors:
  