Microbox snap: wrong application creation error ("zip_archive_support" not supported)
Bug #2067252 reported by
Michele Lo Russo
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Anbox Cloud |
Fix Released
|
Medium
|
Simon Fels |
Bug Description
I was trying to create an application using a zip archive via CLI with the microbox snap, and accidentally forgot to prepend sudo:
ubuntu@
Error: api extension "zip_archive_
But actually, this is not the reason why it failed. The "zip_archive_
ubuntu@
- zip_archive_support
So, this should probably give a different error? (Permission denied, I guess?)
Changed in anbox-cloud: | |
status: | In Progress → Fix Committed |
Changed in anbox-cloud: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
Hey Michele /var/snap/ microbox/ common/ ams/server/ unix.socket) is owned by , microbox/ common/ ams/server/ unix.socket
The microbox snap is running in strict confined mode, the unix domain socket(
```
srw-rw---- 1 root root 0 5月 28 11:00 /var/snap/
```
That's the reason you encountered the above issue.
For the ams charm(regular deployment), we made some tweaks:
1. created the ams group. ams/common/ server/ unix.socket
2. added the current login user to that group.
3. changed the group of the Unix domain socket with:
$ chown :ams /var/snap/
You can do something similar for the microbox to allow running the amc command without sudo.
BR
Gary