[Bug 233207] sysutils/docker-freebsd: Failed to call nmount: File name too long
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Nov 13 20:46:28 UTC 2018
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=233207
Bug ID: 233207
Summary: sysutils/docker-freebsd: Failed to call nmount: File
name too long
Product: Ports & Packages
Version: Latest
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: Individual Port(s)
Assignee: ports-bugs at FreeBSD.org
Reporter: iron.udjin at gmail.com
Hello,
I'm trying to start container:
# docker run -t -i gitlab/gitlab-ce /bin/bash
Error response from daemon: error creating zfs mount of
zroottmp/usr/docker/c1d121894f33d8e0cb4d3e481869ac2ce806f4f6359c1b9fa6fad9afb98520c6-init
to /usr/docker/zfs/graph/c1d121894f33-init: Failed to call nmount: File name
too long
# docker info
Containers: 1
Images: 19
Storage Driver: zfs
Zpool: error while getting pool information exit status 1: "/sbin/zpool zpool
get all -p zroottmp" => cannot open '-p': name must begin with a letter
Zpool Health: not available
Parent Dataset: zroottmp/usr/docker
Space Used By Parent: 1056522240
Space Available: 300252139520
Parent Quota: no
Compression: lz4
Execution Driver: jail
Logging Driver: json-file
Kernel Version: <unknown>
Operating System: <unknown> (error determining if containerized)
CPUs: 8
Total Memory: 0 B
Name: IRON
ID: XMGU:MGYI:3F4L:INTT:KA3T:6LPB:UE2L:AUUO:4COU:BCML:KY4M:6XBA
Debug mode (server): true
File Descriptors: -1
Goroutines: 13
System Time: 2018-11-13T22:38:07.470527183+02:00
EventsListeners: 0
Init SHA1:
Init Path: /usr/local/bin/docker
Docker Root Dir: /usr/docker
WARNING: No memory limit support
WARNING: No swap limit support
# docker version
Client version: 1.7.0-dev
Client API version: 1.19
Go version (client): go1.11.1
Git commit (client): 582db78
OS/Arch (client): freebsd/amd64
Server version: 1.7.0-dev
Server API version: 1.19
Go version (server): go1.11.1
Git commit (server): 582db78
OS/Arch (server): freebsd/amd64
OS: 11.2-STABLE r340361
I guess it's OS related issue which is cannot mount image with long name. Is
there any workaround of it?
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-ports-bugs
mailing list