#Mount not work

40 messages · Page 1 of 1 (latest)

spring pecan
#

I followed all the tutorials about mounts in the web and I didn't get my mounts work. I can't see any files in both side even if I use ls -la command. Don't have any error. Anyone have experienced this and able to help me figure out the problem? Thx.

west merlinBOT
#

Please explain the issue you're experiencing in as much detail as possible. Preferably with error messages in a text format or paste link to logs. Nobody can assist you without information that helps to understand the issue. Help us help you. Messages such as "doesn't work" or "i need help" will most likely be ignored.

wary aspen
#

Did you allow the mounts in your wings config? What do the settings for your mounts look like?

spring pecan
#

Yes\

wary aspen
#

And the wings config part?

spring pecan
wary aspen
#

Have you tried changing the allowed mounts to the specific folder? I don't know if you can allow any mounts in a directory like that.

If it works, another way to achieve the same thing might be trying a wildcard after mounts such as /var/lib/pterodactyl/mounts/*
Not sure if wildcards are supported, but if it works with an exact mount I'd try it.

spring pecan
#

I will try tmr. Thx

wary aspen
#

No problem

tacit wind
#

The mounts are not visible in the container. You'd have to access the mount directly, which is covered in the documentation. Did you run ls on the mount target path and not just for the whole container?

tacit wind
wary aspen
#

Thanks for the correction 👍

spring pecan
#

What do you mean by this? How can I know if it is working or not? Because I do ls in both side (target and source) and I didn't see their difference.

#

And then I do ls /var/lib/pterodactyl/volumes/0699421b-cc90-40d5-a290-f8b9ca7238ab/logs also not see any differences (0699421b-cc90-40d5-a290-f8b9ca7238ab is the mount server)

tacit wind
#

You must ls <mount target> from the container. Please read the mounts documentation

spring pecan
#

Of course I read the mounts documentation

#

The documentation is very unclear unfortunely

#

I tried to change the startup flag to ls <mount target> before, but the container won't start at all.

wary aspen
#

@spring pecan Change the startup command to /bin/bash or if that doesn't exist /bin/sh and you will be able to execute commands and view the output without the server restarting when the command finishes.

wary aspen
# spring pecan

In this case going off your target, you would do ls /logs to see if it exists.

spring pecan
#

Not sure what you mean. /bin/bash?

wary aspen
#

The server will restart when the process created by the start command ends. You can either let it restart and scroll up to see what the output of your command was or open a terminal such as bash.

spring pecan
#

It exists

#

But I have a question. What is the usage of this? Actually I want to mount a plugin folder so that multiple servers can share the same plugin folder by using Mounts. Is that possible?

wary aspen
#

👍

#

Not sure exactly, I don't think it gets used much.

spring pecan
#

Ok

#

I have another question that I can't fix for years.

#

Sometimes, I would like to edit those files in the server (container) directly via FTP or Samba

#

But some error would occurs if I replace some of the files and reload the plugin.

#

It will show something like "permission denied" messages that is related to file system, in the console

#

Anyway to solve this problem

wary aspen
#

No idea, sorry. I haven't had that issue in at least a year. Only happened with really old versions of panel and wings, ie. 1.7.x

tacit wind
tacit wind
# spring pecan Sometimes, I would like to edit those files in the server (container) directly v...

You can't access mount from SFTP or a file manager, only the container can since server volume by itself is a bind mount as well.

If you are referring to modifying normal files, then permissions must be set right - hot reloading without doing so might not work, unless you manually modify permissions or restart the server. Permissions are checked on startup.

Should it be something else, create a new thread/post in support channel the whole error with more details.