Trying to get AIO up again after deleting mastercontainer

ℹ️ Support 📦 Appliances (Docker, Snappy, VM, NCP, AIO)
, , ,
1

Hey there,

I’m still new to the docker world… so the solution to my problem might be really easy but I can’t find it somehow, even not after searching the forum up and down.

environment:
Synology running a freshly installed Ubuntu 22.04 as a VM

Thanks to the very detailed how to I managed to initially start AIO by

sudo docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 80:80 \
--publish 8080:8080 \
--publish 8443:8443 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
nextcloud/all-in-one:latest

made some changes to it, applied backup and everything was running wonderfully.

And then I came up withe the idea that I wanted to access some userfiles on my Synology.
So I mounted two mountpoints. One for backup under /mnt/backup (works!) and one for existing usercontent under /mnt/osna (that worked as well)

so I thought to access the /mnt/osna mountpoint from my AIO I needed to apply
--env NEXTCLOUD_MOUNT="/mnt/osna/“

The “manual” told me
If it was started already, you will need to stop the mastercontainer, remove it (no data will be lost) and recreate it using the docker run command that you initially used).
and so I did…
shutting down all containers via the AIO page then
sudo docker stop nextcloud-aio-mastercontainer
sudo docker container rm nextcloud-aio-mastercontainer

so now I tried to restart everything by the altered sudo docker command like that

sudo docker run \
--init \
--sig-proxy=false \
--name nextcloud-aio-mastercontainer \
--restart always \
--publish 80:80 \
--publish 8080:8080 \
--publish 8443:8443 \
--volume nextcloud_aio_mastercontainer:/mnt/docker-aio-config \
--volume /var/run/docker.sock:/var/run/docker.sock:ro \
--env NEXTCLOUD_MOUNT="/mnt/osna/“ \
nextcloud/all-in-one:latest

but after all this command ends up in a
>
on the screen.

So I think it got stuck somewhere.
What did I make wrong?
And how to proceed?

Any more infos needed? Just let me know.

Looking forward to your suggestions

2

You have a typo here. Advice: look at NEXTCLOUD_MOUNT="/mnt/osna/“ \ :wink:

1 Like
3

ummm… sorry @szaimen for being blond and blind. Meaning: I don’t see the mentioned typo here. Even not with your hint…
And I’m pretty sure if you’d solve the riddle there will be tons of facepalms from me. But I’m ready for it :person_facepalming:

4

Please compare NEXTCLOUD_MOUNT="/mnt/osna/“ with NEXTCLOUD_MOUNT="/mnt/osna/". One of them is correct. (Hint: it is the later one :wink: )

1 Like
5

awwww - that was a hard one :person_facepalming: :person_facepalming: :person_facepalming: :person_facepalming: :person_facepalming: :person_facepalming:

You know what the problem was? I stored the command in a word-document (to have something I could look into afterwards, a kind of personal manual) and apparently word (aka libreoffice writer) exchanged " by “ without me noticing it.

You have sharp eyes, my friend :eyes:

Thanks alot for your support. It seems to work - at least the command runs through now as I write this :heart_eyes_cat:

1 Like