Search Criteria
Package Details: amd-container-toolkit 1.3.0-1
Package Actions
| Git Clone URL: | https://aur.archlinux.org/amd-container-toolkit.git (read-only, click to copy) |
|---|---|
| Package Base: | amd-container-toolkit |
| Description: | Offers tools that streamline the use of AMD GPUs with containers. |
| Upstream URL: | https://github.com/ROCm/container-toolkit |
| Licenses: | Apache-2.0 |
| Submitter: | Lis314 |
| Maintainer: | Lis314 |
| Last Packager: | Lis314 |
| Votes: | 0 |
| Popularity: | 0.000000 |
| First Submitted: | 2026-01-06 16:45 (UTC) |
| Last Updated: | 2026-04-29 06:54 (UTC) |
Dependencies (3)
- docker (rancher-desktop-gitAUR, docker-gitAUR, podman-docker-gitAUR, rancher-desktop-binAUR, rancher-desktopAUR, docker-cli-binAUR, podman-docker)
- git (git-gitAUR, git-glAUR, git-wd40AUR) (make)
- go (go-gitAUR, gcc-go-gitAUR, go-binAUR, goup-rsAUR, gcc-go-snapshotAUR, gcc-go) (make)
Latest Comments
Lolle2000la commented on 2026-02-13 09:35 (UTC)
@Lis314 Thank you, I think that is enough for me!
Lis314 commented on 2026-02-12 22:14 (UTC)
@Lolle2000la Thanks for the patch! Checked it on my side - seems there is no problems. Will this mention do? (i myself don't really know how to correctly acknowledge contributions)
Lolle2000la commented on 2026-02-12 21:19 (UTC)
I'm not quite sure how to properly contribute to a AUR package so I will just add it like this, but basically, I cut
dockerout of the equation entirely and just did what the make files does inside a container.It seems that the execution environment during
makepkgcompletely bars access to the docker socket because ofsystemd-nspawnpolicy, but this works:Lolle2000la commented on 2026-02-11 09:42 (UTC)
I tried to manually run
docker infoand got the following:So the command works in that case but not in the makepkg. The concrete command even works as well on its own:
So why does it not work in the script? Extremely strange.
Lis314 commented on 2026-02-11 09:03 (UTC)
@Lolle2000la Yes, now looking through logs you provided issue is somewhere in your docker daemon. Sadly i can't reproduce it on my end. Looking through new logs, it seems like makepkg can't even run
docker info(i use it to determine if docker is rootless and apply patch if needed)Lolle2000la commented on 2026-02-10 21:01 (UTC)
I tried it, but the error message remained the same.
This makes me think that my docker rootless might be broken, but everything is seemingly fine (containers run fine, no permissions problems there).
Just to make sure it isn't
paruthat is the problem I did try to build it directly withmakepkgLis314 commented on 2026-02-10 20:50 (UTC)
@Lolle2000la I added a patch to handle rootless docker
Lolle2000la commented on 2026-02-10 19:23 (UTC)
This package doesn't appear to build if docker-rootless is installed.