'
(See full trace by running task with --trace)
```
Is this tutorial still up-to-date?
---
### Author:  [@thoka](https://meta.discourse.org/u/thoka)
#### Post date: [March 19, 2023, 10:13pm UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/241 "2023-03-19T22:13:16Z")
To execute the commands (`d/command`) without sudo, you have to add yourself to the `docker` group via
```plaintext
sudo adduser $(whoami) docker
```
and log in again.
---
### Author:  [@GregorSondermeier](https://meta.discourse.org/u/GregorSondermeier)
#### Post date: [March 22, 2023, 8:23am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/242 "2023-03-22T08:23:28Z")
> [@MarcP](#):
>
> After following this tutorial on Ubuntu 22, the d/boot\_dev --init ends with the following output:
Hi,
I’m having that exact same issue.
> [@thoka](#):
>
> To execute the commands (`d/command`) without sudo, you have to add yourself to the `docker` group via
>
> ```plaintext
> sudo adduser $(whoami) docker
>
> ```
>
> and log in again.
I did that:
I have added myself to the _docker_ group and rebooted the system. I verified with the `groups` command that I am indeed part of the _docker_ group.
Still this error keeps popping up.
I’m on Ubuntu 22.04 and I already had docker installed via docker desktop for other projects. The user account I’m working with does not have admin privileges (is not part of the sudo group), but I have access to an account that does. However I can’t use that other account for my daily work.
Is that a problem?
---
### Author:  [@thoka](https://meta.discourse.org/u/thoka)
#### Post date: [March 24, 2023, 6:53am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/243 "2023-03-24T06:53:39Z")
> [@GregorSondermeier](#):
>
> I’m on Ubuntu 22.04 and I already had docker installed via docker desktop for other projects.
Hm. Are you on a bare metal Ubuntu 22.04 or running it as wsl vm ?
---
### Author:  [@GregorSondermeier](https://meta.discourse.org/u/GregorSondermeier)
#### Post date: [March 24, 2023, 10:13am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/244 "2023-03-24T10:13:01Z")
Bare metal. Ubuntu 22.04 running natively on my work laptop.
I noticed the following:
The container’s _/src_ folder is mounted to _/home/gregor/repos/discourse_ on my host machine:
On my host machine, after pulling the git repo this folder belongs to me and my group:
```bash
repos $ whoami
gregor
repos $ groups
gregor docker
repos $ pwd
/home/gregor/repos
repos $ ll
[...]
drwxrwxr-x 21 gregor gregor 4096 Mär 24 10:57 discourse/
[...]
```
The `d/*` scripts execute all commands inside the docker container as the _discourse_ user ([see here](https://github.com/discourse/discourse/blob/main/bin/docker/exec#L5)). And that discourse user does not have write access to that mounted _/src_ folder.
```plaintext
rake aborted!
Discourse::Utils::CommandError: /src/lib/discourse.rb:137:in `exec': mkdir: cannot create directory ‘/src/public/plugins/’: Permission denied
```
I can reproduce this if I log in to the container and try to create folders in there. If I do it as the root user, it succeeds.
On my host machine:
If I do it as the discourse user, it fails:
However, I can’t quite connect this together 🤔
---
### Author:  [@thoka](https://meta.discourse.org/u/thoka)
#### Post date: [March 24, 2023, 10:54am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/245 "2023-03-24T10:54:35Z")
Hm. I run ubuntu 22.04 inside wsl in windows:
After `d/shell`:
and
```plaintext
$ docker inspect -f "{{ .Mounts }}" discourse_dev
[{bind /home/toka/dv/discourse/discourse/data/postgres /shared/postgres_data delegated true rprivate}
{bind /home/toka/dv/discourse/discourse /src delegated true rprivate}]
```
---
### Author:  [@ClawdiaWolf](https://meta.discourse.org/u/ClawdiaWolf)
#### Post date: [March 24, 2023, 11:12am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/246 "2023-03-24T11:12:58Z")
> [@GregorSondermeier](#):
>
> The `d/*` scripts execute all commands inside the docker container as the _discourse_ user ([see here](https://github.com/discourse/discourse/blob/main/bin/docker/exec#L5)). And that discourse user does not have write access to that mounted _/src_ folder.
>
> ```plaintext
>
> ```
Is your UID on the host different than 1000 by any chance? If so that’s where the issue is. The Discourse user inside Docker is UID 1000 so the host files need to be writable by UID 1000
---
### Author:  [@GregorSondermeier](https://meta.discourse.org/u/GregorSondermeier)
#### Post date: [March 24, 2023, 11:16am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/247 "2023-03-24T11:16:30Z")
[This SO post](https://stackoverflow.com/a/45673309/3628926) has hinted me to the same direction as you did. I can confirm that both my _gregor_ user on the host machine and the _discourse_ user in the container have the same ID 1000.
---
### Author:  [@thoka](https://meta.discourse.org/u/thoka)
#### Post date: [March 24, 2023, 11:52am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/249 "2023-03-24T11:52:34Z")
What’s the output of `d/exec ls -lan` and `echo $UID`?
---
### Author:  [@GregorSondermeier](https://meta.discourse.org/u/GregorSondermeier)
#### Post date: [March 24, 2023, 11:57am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/250 "2023-03-24T11:57:08Z")
After running `d/shell`:
I see that all files are owned by root and not by discourse like on your screenshot.
(I had a previous post which showed nobody/nogroup, which was misleading because I fiddled around with creating a _discourse_ user and group on my host machine, which led to no success. So I deleted the post)
---
### Author:  [@GregorSondermeier](https://meta.discourse.org/u/GregorSondermeier)
#### Post date: [March 24, 2023, 11:59am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/251 "2023-03-24T11:59:36Z")
Indicates that all files inside _/src_ are owned by the root user.
(The discourse group comes from an earlier attempt which wasn’t fruitful)
Thanks a lot for your help btw. I feel a bit stupid, I must be missing some knowledge about the unix permission system.
---
### Author:  [@GregorSondermeier](https://meta.discourse.org/u/GregorSondermeier)
#### Post date: [March 27, 2023, 11:26am UTC](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009/252 "2023-03-27T11:26:51Z")
After much research and fiddling around I have learned that **Docker Desktop on Linux** is causing the permission issues.
You see, the Discourse application in the Docker container is run as as a non-root user, namely the [discourse](https://github.com/discourse/discourse/blob/main/bin/docker/exec#L5) user. But as written e.g. [here](https://forums.docker.com/t/bind-mount-permissions-unexpected-mounting-as-root-root/129328) and [here](https://stackoverflow.com/a/50820023/3628926):
> Docker Desktop on Linux runs a virtual machine and the containers will run inside that virtual machine. In that case you can’t just mount the host folder the same way into the containers, because you need to mount it first into the virtual machine.
So, as someone who is by all means not a Docker expert, I see two ways of addressing this issue:
**(1) Ditch Docker Desktop on Linux and run Docker natively instead**
This seems to be the most sustainable solution as I see that the discourse container seems to be designed to be used like that. I’m only hesistant because then I have to remember all the commands to manage my images, containers and resources. And, being a frontent dev, I’d rather fancy an UI to manage stuff. But I guess I have to approach this as an investment to learn more about Docker.
**OR**
**(2) Change ownership of the folders mounted into the container**
I managed to get this approach to work and successfully run Discourse locally from Docker Desktop, however I do see a bunch of warnings in the Terminal and therefore I’m not sure how sustainable this solution is in the long run.
This involves several steps:
**Step 1: Clone the Repo**
```sh
$ git clone https://github.com/discourse/discourse.git
$ cd discourse
```
**Step 2: Initialize Container**
From within the cloned _discourse_ folder on the host machine, execute:
```plaintext
$ d/boot_dev
```
What does it do? See [here](https://github.com/discourse/discourse/blob/main/bin/docker/boot_dev).
**Important** : Omit the `--init` flag so that nothing will be done after the container creation.
**Step 3: Change owner of folders**
The discourse user within the docker container has the id `1000`. This guide assumes that your host machine’s user also has that same id. It might not break things if your host machine’s user has a different id, but I cannot test this and therefore can’t speak for this situation. You can find out your id by executing `id` or `echo $UID` in a linux terminal.
From your host machine, execute:
```sh
# open a shell in the docker container
$ d/shell
# you should already be in /src, bug just for good measure:
$ cd /src
# change the owner of /src to the discourse user and group
$ chown 1000:1000 .
# change the owner of all files and folders within /src to the discourse user and group (non-recursively)
$ chown 1000:1000 *
# recursively change the owner of almost all subfolders to the discourse user and group
# basically all folders except 'database', because that one belongs to the 'postgres' user and group
$ chown -R 1000:1000 app bin config d db docs documentation images lib log plugins public script spec test vendor
# verify that it has worked, should show the discourse user and group now
$ ls -l
# leave the container
$ exit
```
**Step 4: Continue as usual**
Continue setting up the container and starting Discourse by executing the following from your host machine:
```sh
# install gems
$ d/bundle install
# migrate database
$ d/rake db:migrate
$ RAILS_ENV=test d/rake db:migrate
# create admin user
$ d/rake admin:create
# In one terminal:
d/rails s
# And in a separate terminal
d/ember-cli
```
Note:
I faced some warnings like this:
`fatal: detected dubious ownership in repository at '/src'`
Which comes from the Docker Desktop on Linux virtualization thing.
Do ignore these warnings, from your host machine, execute:
```plaintext
d/exec git config --global --add safe.directory /src
```
**Why does Docker Desktop for Linux run a VM?**
> **[FAQs for Docker Desktop for Linux](https://docs.docker.com/desktop/troubleshoot-and-support/faqs/linuxfaqs/)**
>
> Frequently asked questions for Docker Desktop for Linux
[Previous page](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009.md?page=7)
[Next page](https://meta.discourse.org/t/install-discourse-for-development-using-docker/102009.md?page=9)