@ibacher I used some recommendations regardin to host configuration from here
opened 08:56AM - 31 Mar 18 UTC
closed 10:56PM - 09 Nov 21 UTC
<!--
This issue tracker is for *bug reports* and *feature requests*.
For quest… ions, and getting help on using docker:
- Docker documentation - https://docs.docker.com
- Docker Forums - https://forums.docker.com
- Docker community Slack - https://dockercommunity.slack.com/ (register here: http://dockr.ly/community)
- Post a question on StackOverflow, using the Docker tag
-->
* [ ] This is a bug report
* [x] This is a feature request
* [x] I searched existing issues before opening this one
<!--
DO NOT report security issues publicly! If you suspect you discovered
a security issue, send your report privately to security@docker.com.
-->
### Expected behavior
As in [docker-for-mac](https://docs.docker.com/docker-for-mac/release-notes/#stable-releases-of-2018) and docker-for-windows, inside a container, the DNS name `host.docker.internal` resolves to an IP address allowing network access to the host (roughly the output of `ip -4 route list match 0/0 | cut -d' ' -f3` inside the same container).
### Actual behavior
`host.docker.internal` resolves to nothing
### Steps to reproduce the behavior
Execute `docker run --rm alpine nslookup host.docker.internal`
See it returns `nslookup: can't resolve 'host.docker.internal': Name does not resolve`
<!--
Describe the exact steps to reproduce. If possible, provide a *minimum*
reproduction example; take into account that others do not have access
to your private images, source code, and environment.
REMOVE SENSITIVE DATA BEFORE POSTING (replace those parts with "REDACTED")
-->
**Output of `docker version`:**
```
Client:
Version: 18.03.0-ce
API version: 1.37
Go version: go1.9.4
Git commit: 0520e24
Built: Wed Mar 21 23:10:09 2018
OS/Arch: linux/amd64
Experimental: false
Orchestrator: swarm
Server:
Engine:
Version: 18.03.0-ce
API version: 1.37 (minimum version 1.12)
Go version: go1.9.4
Git commit: 0520e24
Built: Wed Mar 21 23:08:36 2018
OS/Arch: linux/amd64
Experimental: false
```
**Output of `docker info`:**
```
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 18.03.0-ce
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Native Overlay Diff: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
Volume: local
Network: bridge host macvlan null overlay
Log: awslogs fluentd gcplogs gelf journald json-file logentries splunk syslog
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: cfd04396dc68220d1cecbe686a6cc3aa5ce3667c
runc version: 4fc53a81fb7c994640722ac585fa9ca548971871
init version: 949e6fa
Security Options:
apparmor
seccomp
Profile: default
Kernel Version: 4.13.0-37-generic
Operating System: Ubuntu 17.10
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.947GiB
Name: rob-VirtualBox
ID: 3L2C:BTV3:TQO2:4SAG:XVW5:744G:MPWQ:62FK:56DP:KH3Z:EQ7Z:TBR5
Docker Root Dir: /var/lib/docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Labels:
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
WARNING: No swap limit support
```
**Additional environment details (AWS, VirtualBox, physical, etc.)**
Running Ubuntu in VirtualBox 5.2.8 on OS/X 10.13.4
and it worked, I could get patient data and some observations.
but there are a lot of another problems:
http://localhost:8080/openmrs/ws/fhir2/R4/Device?_pretty=false&patient=1aaeea9e-4adf-4337-9b76-35863e842216&_count=1000
Status Code: 404 Not Found
response:
{"resourceType":"OperationOutcome","text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h1>Operation Outcome</h1><table border=\"0\"><tr><td style=\"font-weight: bold;\">ERROR</td><td>[]</td><td><pre>Unknown resource type 'Device' - Server knows how to handle: [Condition, Group, MedicationRequest, Task, Immunization, Patient, DiagnosticReport, RelatedPerson, ServiceRequest, Practitioner, AllergyIntolerance, Observation, Medication, Encounter, Person, OperationDefinition, Location]</pre></td>\n\t\t\t</tr>\n\t\t</table>\n\t</div>"},"issue":[{"severity":"error","code":"processing","diagnostics":"Unknown resource type 'Device' - Server knows how to handle: [Condition, Group, MedicationRequest, Task, Immunization, Patient, DiagnosticReport, RelatedPerson, ServiceRequest, Practitioner, AllergyIntolerance, Observation, Medication, Encounter, Person, OperationDefinition, Location]"}]}
http://localhost:8080/openmrs/ws/fhir2/R4/Flag?date=>=2022-02-21T04:48:43.589Z&subject=1aaeea9e-4adf-4337-9b76-35863e842216&identifier=system:sureAlert|74018-3,system:sureAlert|76281-5,system:sureAlert|74385-9&_count=200&_sort=date&_pretty=false
Status Code: 404 Not Found
response:
{"resourceType":"OperationOutcome","text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h1>Operation Outcome</h1><table border=\"0\"><tr><td style=\"font-weight: bold;\">ERROR</td><td>[]</td><td><pre>Unknown resource type 'Flag' - Server knows how to handle: [Condition, Group, MedicationRequest, Task, Immunization, Patient, DiagnosticReport, RelatedPerson, ServiceRequest, Practitioner, AllergyIntolerance, Observation, Medication, Encounter, Person, OperationDefinition, Location]</pre></td>\n\t\t\t</tr>\n\t\t</table>\n\t</div>"},"issue":[{"severity":"error","code":"processing","diagnostics":"Unknown resource type 'Flag' - Server knows how to handle: [Condition, Group, MedicationRequest, Task, Immunization, Patient, DiagnosticReport, RelatedPerson, ServiceRequest, Practitioner, AllergyIntolerance, Observation, Medication, Encounter, Person, OperationDefinition, Location]"}]}
http://localhost:8080/openmrs/ws/fhir2/R4/Media?subject=1aaeea9e-4adf-4337-9b76-35863e842216&_sort:desc=created&_count=5&status=completed&_pretty=false
Status Code: 404 Not Found
response:
{"resourceType":"OperationOutcome","text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h1>Operation Outcome</h1><table border=\"0\"><tr><td style=\"font-weight: bold;\">ERROR</td><td>[]</td><td><pre>Unknown resource type 'Media' - Server knows how to handle: [Condition, Group, MedicationRequest, Task, Immunization, Patient, DiagnosticReport, RelatedPerson, ServiceRequest, Practitioner, AllergyIntolerance, Observation, Medication, Encounter, Person, OperationDefinition, Location]</pre></td>\n\t\t\t</tr>\n\t\t</table>\n\t</div>"},"issue":[{"severity":"error","code":"processing","diagnostics":"Unknown resource type 'Media' - Server knows how to handle: [Condition, Group, MedicationRequest, Task, Immunization, Patient, DiagnosticReport, RelatedPerson, ServiceRequest, Practitioner, AllergyIntolerance, Observation, Medication, Encounter, Person, OperationDefinition, Location]"}]}
http://localhost:8080/openmrs/ws/fhir2/R4/DiagnosticReport?subject=1aaeea9e-4adf-4337-9b76-35863e842216&code=131328&date=>=2022-01-22T07:48:45.990Z&date=<=2022-02-21T07:48:45.990Z&_count=1&_sort:desc=_lastUpdated&_pretty=false
Status Code: 400 Bad Request
response:
{"resourceType":"OperationOutcome","text":{"status":"generated","div":"<div xmlns=\"http://www.w3.org/1999/xhtml\"><h1>Operation Outcome</h1><table border=\"0\"><tr><td style=\"font-weight: bold;\">ERROR</td><td>[]</td><td><pre>Invalid request: The FHIR endpoint on this server does not know how to handle GET operation[DiagnosticReport] with parameters [[date, _pretty, _count, code, _sort:desc, subject]]</pre></td>\n\t\t\t</tr>\n\t\t</table>\n\t</div>"},"issue":[{"severity":"error","code":"not-supported","diagnostics":"Invalid request: The FHIR endpoint on this server does not know how to handle GET operation[DiagnosticReport] with parameters [[date, _pretty, _count, code, _sort:desc, subject]]"}]}
Why there are no some endpoints?