[ https://issues.jboss.org/browse/JBIDE-21059?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21059: ------------------------------------- So I've done as [~xcoulon] suggested. Here are the steps / results: After doing all that xavier said, I then: 1) Find the IP of the host: a) docker ps b) docker inspect afb24bf61660 | grep IPAddress | cut -d '"' -f 4 2) Create a new wf10 server adapter a) New -> server -> wildfly 10.0 b) host: take value from 1.b c) press next to 2nd page d) select remote + management e) check the 'externally managed' box f) Finish 3) right-click server, select debug server 4) Verify server is eventually set to 'Debugging...' 5) verify connection is created Some small issues: 1) The management poller only kinda work. It recognizes the server is telling us our credentials have failed, and so it treats that as the server is up. 2) Since no management credentials are set up, deployment probably won't really work either. Are there any specific usecases or workflows we'd like to encourage and improve for this? How do you imagine this being used by the user? I imagine if we map folders in, then they could use filesystem deployment instead, however our tools won't really like that. We'd have a hostname of some ip address that we can't ssh into, and the server is designed to treat remote + filesystem to use ssh. An alternative is to use the port mappings you set up in the dockerfile, add some folder mappings, and edit the ports in the server editor to be the mapped ports. Both seem a bit complicated for the user, really. Finally, when "stopping" the server, we don't disconnect the debugger, so it just kinda stays there. That's... not optimal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)