Having any issues installing YAMS? This is the place to ask!
daiki
Posts: 3 Joined: Wed Apr 09, 2025 1:20 pm
Post
by daiki » Wed Apr 09, 2025 1:25 pm
Hi,
wanted to install YAMS on a fresh clean VM on proxmox.
During the install script I get the following error:
Code: Select all
Using Mullvad username as password
Configuring the docker-compose file for user "yams" in "/opt/yams"...
Copying .env.example to /opt/yams/.env...
.env.example copied successfully ✅
Copying docker-compose.example.yaml to /opt/yams/docker-compose.yaml...
docker-compose.example.yaml copied successfully ✅
Copying docker-compose.custom.yaml to /opt/yams/docker-compose.custom.yaml...
docker-compose.custom.yaml copied successfully ✅
Updating environment configuration...
Updating docker-compose configuration...
Configuring VPN settings...
Updating YAMS CLI configuration...
sed: Temporäre Datei ./sedqBv52U kann nicht geöffnet werden: Keine Berechtigung
Failed to update YAMS CLI script
Last line is: sed: couldn't open temporary file ./sedqBv52U: Permission denied
Any idea how to solve this?
Regards
rogs
Site Admin
Posts: 307 Joined: Mon Oct 23, 2023 12:53 pm
Location: Montevideo, Uruguay
Gender:
Contact:
Post
by rogs » Wed Apr 09, 2025 5:56 pm
Hey @daiki !
What's your OS?
What version of docker are you using? (the output of which docker
)
Do you have enough permissions?
Cheers!
Roger.
daiki
Posts: 3 Joined: Wed Apr 09, 2025 1:20 pm
Post
by daiki » Wed Apr 09, 2025 7:17 pm
Hi rogs,
thx for your reply. Sorry should have that included in the first post.
It's a new fresh Debian 12 vm (not lxc) in a proxmox 8.3 host.
All updated.
docker
Code: Select all
yams@yams:~$ which docker
/usr/bin/docker
yams@yams:~$ docker version
Client: Docker Engine - Community
Version: 28.0.4
API version: 1.48
Go version: go1.23.7
Git commit: b8034c0
Built: Tue Mar 25 15:07:22 2025
OS/Arch: linux/amd64
Context: default
Server: Docker Engine - Community
Engine:
Version: 28.0.4
API version: 1.48 (minimum version 1.24)
Go version: go1.23.7
Git commit: 6430e49
Built: Tue Mar 25 15:07:22 2025
OS/Arch: linux/amd64
Experimental: false
containerd:
Version: 1.7.27
GitCommit: 05044ec0a9a75232cad458027ca83437aae3f4da
runc:
Version: 1.2.5
GitCommit: v1.2.5-0-g59923ef
docker-init:
Version: 0.19.0
GitCommit: de40ad0
Code: Select all
yams@yams:~$ ls -ahl /opt/yams
insgesamt 24K
drwxr-xr-x 2 yams yams 4,0K 9. Apr 15:16 .
drwxr-xr-x 4 root root 4,0K 8. Apr 11:54 ..
-rw-r--r-- 1 yams yams 159 9. Apr 15:16 docker-compose.custom.yaml
-rw-r--r-- 1 yams yams 5,3K 9. Apr 15:16 docker-compose.yaml
-rw-r--r-- 1 yams yams 228 9. Apr 15:16 .env
yams@yams:~$ ls -ahl /opt
insgesamt 16K
drwxr-xr-x 4 root root 4,0K 8. Apr 11:54 .
drwxr-xr-x 18 root root 4,0K 8. Apr 11:08 ..
drwx--x--x 4 root root 4,0K 8. Apr 11:54 containerd
drwxr-xr-x 2 yams yams 4,0K 9. Apr 15:16 yams
The user yams can use sudo.
If you need any more information just tell me.
Thanks!
rogs
Site Admin
Posts: 307 Joined: Mon Oct 23, 2023 12:53 pm
Location: Montevideo, Uruguay
Gender:
Contact:
Post
by rogs » Wed Apr 09, 2025 7:32 pm
That is actually perfect, thank you!
Everything looks fine, the .env
file is there. Did you try the install again? Do you have the yams
script available?
I have never seen this error. It's failing on a sed
, which leads me to believe there's a permission error either on /opt/yams
(which you just proved there is not), or the place where you cloned yams
. Maybe try cloning yams
somewhere else where you know for sure the yams
user has permissions
Cheers!
Roger.
daiki
Posts: 3 Joined: Wed Apr 09, 2025 1:20 pm
Post
by daiki » Wed Apr 09, 2025 9:11 pm
I tried running the install script some times more.
Even rebooted the vm and rerun the script. Always the Same result.
But I found a solution for my case.
The scripts clones to /tmp/yams.
This folder was owned by root:root.
I've chown'd to my user yams and rerun the script.
Now without errors.
Thanks for the help!
Looking forward to configure.. tomorrow
rogs
Site Admin
Posts: 307 Joined: Mon Oct 23, 2023 12:53 pm
Location: Montevideo, Uruguay
Gender:
Contact:
Post
by rogs » Wed Apr 09, 2025 9:18 pm
Excellent! That was what I thought then, a permissions issue where you cloned the repo. Maybe you cloned it with root and then changed to your user.
I'm glad you were able to fix it!