I haven’t written a docker-compose.yml before, wouldn’t it be company specific?
Can you show me and example of one you think it should look like?
@sickcodes commented on GitHub (Jun 8, 2020):
There’s a Dockerfile already in the repo.
I haven’t written a docker-compose.yml before, wouldn’t it be company specific?
Can you show me and example of one you think it should look like?
Have you ran the VNC version? You can detach that one, runs out of the box, no need to worry about displays.
@sickcodes commented on GitHub (Jun 8, 2020):
Have you ran the VNC version? You can detach that one, runs out of the box, no need to worry about displays.
This builds on one of the closed issues https://github.com/sickcodes/Docker-OSX/issues/1 so it includes the cap and the net portions that's not in the current readme.(didn't see it before) I'm running pop os 20.04 if that matters.
@parasquid commented on GitHub (Jun 8, 2020):
funnily enough, I wrote one just now (was searching for a way to automate the build).
``` yaml
version: '3.1'
services:
osx:
image: sickcodes/docker-osx
privileged: true
environment:
DISPLAY: ${DISPLAY:-:0.0}
network_mode: "host"
cap_add:
- ALL
volumes:
- ./tmp/.X11-unix:/tmp/.X11-unix
```
This builds on one of the closed issues https://github.com/sickcodes/Docker-OSX/issues/1 so it includes the `cap` and the `net` portions ~that's not in the current readme.~(didn't see it before) I'm running pop os 20.04 if that matters.
@parasquid commented on GitHub (Jun 8, 2020):
This is generally how it looks like:

One advantage of using docker-compose is that if you run docker-compose up on the same docker-compose.yml file it will bring up the same container (no need to start the docker image manually as in the readme)
@parasquid commented on GitHub (Jun 8, 2020):
One advantage of using docker-compose is that if you run `docker-compose up` on the same docker-compose.yml file it will bring up the same container (no need to start the docker image manually as in the readme)
Right! So no more docker ps bash commands? Do you mind if I integrate the file you commented? Or do you want to write a pull request?
@sickcodes commented on GitHub (Jun 8, 2020):
Right! So no more docker ps bash commands? Do you mind if I integrate the file you commented? Or do you want to write a pull request?
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @ralyodio on GitHub (Jun 8, 2020).
Can we get an out of the box working docker-compose.yml and Dockerfile?
@sickcodes commented on GitHub (Jun 8, 2020):
There’s a Dockerfile already in the repo.
I haven’t written a docker-compose.yml before, wouldn’t it be company specific?
Can you show me and example of one you think it should look like?
@sickcodes commented on GitHub (Jun 8, 2020):
Have you ran the VNC version? You can detach that one, runs out of the box, no need to worry about displays.
@parasquid commented on GitHub (Jun 8, 2020):
funnily enough, I wrote one just now (was searching for a way to automate the build).
This builds on one of the closed issues https://github.com/sickcodes/Docker-OSX/issues/1 so it includes the
capand thenetportionsthat's not in the current readme.(didn't see it before) I'm running pop os 20.04 if that matters.@parasquid commented on GitHub (Jun 8, 2020):
This is generally how it looks like:

@parasquid commented on GitHub (Jun 8, 2020):
One advantage of using docker-compose is that if you run
docker-compose upon the same docker-compose.yml file it will bring up the same container (no need to start the docker image manually as in the readme)@sickcodes commented on GitHub (Jun 8, 2020):
Right! So no more docker ps bash commands? Do you mind if I integrate the file you commented? Or do you want to write a pull request?
@parasquid commented on GitHub (Jun 8, 2020):
PR is here https://github.com/sickcodes/Docker-OSX/pull/25 :)