You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
sudo pot init
sudo pot create-base -r 11.2
sudo pot create -p committer-pot -b 11.2
sudo pot create-fscomp -f svn-ports
sudo pot create-fscomp -f svn-src
sudo pot create-fscomp -f svn-doc
sudo pot add-fscomp -p committer-pot -f svn-src -m ~/freebsd/svn/src/
sudo pot add-fscomp -p committer-pot -f svn-ports -m ~/freebsd/svn/ports/
sudo pot add-fscomp -p committer-pot -f svn-doc -m ~/freebsd/svn/doc/
sudo pot snapshot -p committer-pot
sudo pot start committer-pot
As a result of the last command I got:
mount_nullfs: /opt/pot/jails/committer-pot/m/home: No such file or directory
###> Error mounting /opt/pot/fscomp/svn-src
ifconfig: interface destroy does not exist
###> Mount failed
It happens every time I try to run sudo pot start committer-pot.
The text was updated successfully, but these errors were encountered:
I'm able to reproduce the error.
The problem is the expansion of ~ , that happen outside the container, so it would try to use the $HOME of the current user.
The real problem, here, is that it's quite hard to validate the argument of the -m option
If you use an existing absolute pathname (like /mnt) you are fine, but there is room from improvement for sure
Here's what I've done:
As a result of the last command I got:
It happens every time I try to run
sudo pot start committer-pot
.The text was updated successfully, but these errors were encountered: