Skip to content

Added sandbox and nolibfuse test#2292

Merged
ivan-hc merged 6 commits intoivan-hc:mainfrom
vishnu350:main
Apr 22, 2026
Merged

Added sandbox and nolibfuse test#2292
ivan-hc merged 6 commits intoivan-hc:mainfrom
vishnu350:main

Conversation

@vishnu350
Copy link
Copy Markdown
Contributor

@vishnu350 vishnu350 commented Apr 22, 2026

Regression updates:

  • Added sandbox and nolibfuse test.
  • Added new tests to regression list.
  • Added symlink cleanup in remove_all_apps functions (needed for tmpfs dirs)
  • Updated podman run command in README to support sandboxing.

I am not able to get sas to work in a container, this sandbox test uses aisap for now. The test uses an automated way to check file access to confirm if it worked, so next time if sandboxing is broken we will know.

@ivan-hc ivan-hc merged commit be9156e into ivan-hc:main Apr 22, 2026
@fiftydinar
Copy link
Copy Markdown
Contributor

I am not able to get sas to work in a container, this sandbox test uses aisap for now.

@Samueru-sama

@ivan-hc
Copy link
Copy Markdown
Owner

ivan-hc commented Apr 24, 2026

@vishnu350 are you on Ubuntu?

@Samueru-sama
Copy link
Copy Markdown
Contributor

I am not able to get sas to work in a container, this sandbox test uses aisap for now.

@Samueru-sama

#2282 (comment)

@vishnu350
Copy link
Copy Markdown
Contributor Author

@vishnu350 are you on Ubuntu?

The problem with sas is only inside the am-debian/am-ubuntu testing container. It works fine outside.

#2282 (comment)

I went through it, I think the issue is this line:
USER="${LOGNAME:-${USER:-${USERNAME}}}"

All of those env variables are not set in the container.

This is what /etc/passwd looks like:
root:x:0:0:root:/root:/bin/bash

@Samueru-sama
Copy link
Copy Markdown
Contributor

@vishnu350 are you on Ubuntu?

The problem with sas is only inside the am-debian/am-ubuntu testing container. It works fine outside.

#2282 (comment)

I went through it, I think the issue is this line: USER="${LOGNAME:-${USER:-${USERNAME}}}"

All of those env variables are not set in the container.

This is what /etc/passwd looks like: root:x:0:0:root:/root:/bin/bash

Well set the var in the container if empty then.

POSIX mandates LOGNAME to be set upon user login.

@vishnu350
Copy link
Copy Markdown
Contributor Author

Hi @Samueru-sama. I did try that a few days back, but ran into other issues and then gave up.

Anyway, I tried again and got it to work. First step is to set the missing vars:
export USER=root
export USERNAME=root
export LOGNAME=root

The next problem is it needs /run/user dir with ID (0 for root user in container):
mkfifo: cannot create fifo '/run/user/0/sas-xdg-open-pipe': No such file or directory

So I just create that dir since /run/user is not shared by the system with the container:
mkdir -p /run/user/0 && chmod 777 /run/user/0

Next error is:
bwrap: Can't create file at /bin/xdg-open: Read-only file system

So I figured that I have to cave in and just install xdg-utils which is a 373MB install. The whole am-debian container is only 200MB+, so it is quite a big install.
apt install xdg-utils

After that sas works in the container. But is there a way to do this without installing xdg-utils?

@Samueru-sama
Copy link
Copy Markdown
Contributor

But is there a way to do this without installing xdg-utils?

Pass --no-xdgopen flag to sas.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants