flipboard.social is one of the many independent Mastodon servers you can use to participate in the fediverse.
Welcome to Flipboard on Mastodon. A place for our community of curators and enthusiasts to inform and inspire each other. If you'd like to join please request an invitation via the sign-up page.

Administered by:

Server stats:

1.3K
active users

#mount

1 post1 participant0 posts today

alojapan.com/1227070/mount-fuj Mount Fuji views are diamond in rough for foreign golfers #are #Diamond #Foreign #fuji #Golfers #mount #MountFuji #MountFujiTopics #MountFuji #rough #Views #富士山 SHIZUOKA, Japan — Shizuoka prefecture, south of Tokyo, is promoting tour packages for wealthy golfers from abroad. A major selling point is the views the courses offer of Mount Fuji, which golfers can enjoy while playing. The prefecture hopes to promote longer stays and greater spendi…

alojapan.com/1223394/asian-tou Asian tourists flock to Mount Fuji for the perfect shot #asian #flock #fuji #mount #MountFuji #MountFujiTopics #MountFuji #perfect #shot #tourists FUJIYOSHIDA, Japan — The quest to share an iconic image of Japan on social media is driving a tourist boom near Mount Fuji that is spreading far beyond the beaten track. Fujiyoshida, formerly a relatively little-known city close to the iconic mountain, started to attract more visitors after the pea…

Docker-Compose and automatic mounts

If you want your Docker container to use data from a network share, people tend to mount the share to a directory outside of Docker and then point the Docker volume to that mounted path. However, Docker-Compose also supports mounting volumes and brings some advantages. E.g. for a SMB/CIFS share, the relevant parts in your compose file could look like this: services: my-service: ... volumes: - my-smb-share:/data:rw volumes: my-smb-share: driver_opts: […]

blog.mbirth.uk/2025/02/01/dock

blog.mbirth.ukDocker-Compose and automatic mounts – blog.mbirth.uk
More from Markus Birth
It seems that #Thunar ( #Xubuntu default file manager ) just can't get the .Trash folder to work with #btrfs volumes using subvol #mount option. That's quite a weak achievement. Because the #swapfile must be on root volume, and therefore it's logical to use subvolume for all data, so it can be snapshotted. But if snapshots are being used, then #trash feature won't work anymore, due to the limitations linked to the #subvolumes. Yet I personally find this to be incredibly lame and totally pointless and completely unbased limitation. #Linux silliness.